3d76c30354
* CI: Document the 'all-in-one' layout + small refactoring (#10725) * Rename aio to all-in-one and document it ADTM. Acronyms don't tell much. * Refactor vm_count in tests provisioning * Add test case for calico using etcd datastore (#10722) * Add multinode ci layout * Add test case for calico using etcd datastore * Fix calico-node in etcd mode (#10438) * Calico : add ETCD endpoints to install-cni container * Calico : remove nodename from configmap in etcd mode --------- Co-authored-by: Olivier Levitt <olivier.levitt@gmail.com>
38 lines
1.6 KiB
Markdown
38 lines
1.6 KiB
Markdown
# Node Layouts
|
|
|
|
There are six node layout types: `default`, `separate`, `ha`, `scale`, `all-in-one`, and `multinode`.
|
|
|
|
`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.
|
|
|
|
`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.
|
|
|
|
`all-in-one` layout use a single node for with `kube_control_plane`, `etcd` and `kube_node` merged.
|
|
|
|
`multinode` layout consists of two separate `kube_node` and a merged single `etcd+kube_control_plane` node.
|
|
|
|
Note, the canal network plugin deploys flannel as well plus calico policy controller.
|
|
|
|
## Test cases
|
|
|
|
The [CI Matrix](/docs/ci.md) 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`.
|