richard
/
kubespray
mirror of https://github.com/kubernetes-sigs/kubespray.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
7940 Commits
29 Branches
81 Tags
150 MiB
 
 
 
 
 
Tree: d23753e9f7
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'd23753e9f7'
${ noResults }
kubespray/docs/developers/test_cases.md

1.5 KiB
Raw Blame History

Node Layouts

There are five node layout types: default, separate, ha, all-in-one, and node-etcd-client.

default is a non-HA two nodes setup with one separate kube_node and the etcd group merged with the kube_control_plane.

separate layout is when there is only node of each type, which includes a kube_control_plane, kube_node, and etcd cluster member.

ha layout consists of two etcd nodes, two control planes and a single worker node, with role intersection.

all-in-one layout use a single node for with kube_control_plane, etcd and kube_node merged.

node-etcd-client layout consists of a 4 nodes cluster, all of them in kube_node, first 3 in etcd and only one kube_control_plane. This is necessary to tests setups requiring that nodes are etcd clients (use of cilium as network_plugin for instance)

Note, the canal network plugin deploys flannel as well plus calico policy controller.

Test cases

The CI Matrix displays OS, Network Plugin and Container Manager tested.

All tests are breakdown into 3 "stages" ("Stage" means a build step of the build pipeline) as follows:

  • unit_tests: Linting, markdown, vagrant & terraform validation etc...
  • part1: Molecule and AIO tests
  • part2: Standard tests with different layouts and OS/Runtime/Network
  • part3: Upgrade jobs, terraform jobs and recover control plane tests
  • special: Other jobs (manuals)

The steps are ordered as unit_tests->part1->part2->part3->special.