360aff4a57
* rename ansible groups to use _ instead of -
k8s-cluster -> k8s_cluster
k8s-node -> k8s_node
calico-rr -> calico_rr
no-floating -> no_floating
Note: kube-node,k8s-cluster groups in upgrade CI
need clean-up after v2.16 is tagged
* ensure old groups are mapped to the new ones
1.4 KiB
Node Layouts
There are four node layout types: default, separate, ha, and scale.
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 masters and a single worker node,
with role intersection.
scale layout can be combined with above layouts (ha-scale, separate-scale). It includes 200 fake hosts
in the Ansible inventory. This helps test TLS certificate generation at scale
to prevent regressions and profile certain long-running tasks. These nodes are
never actually deployed, but certificates are generated for them.
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.