486b223e01
This replaces kube-master with kube_control_plane because of [1]:
The Kubernetes project is moving away from wording that is
considered offensive. A new working group WG Naming was created
to track this work, and the word "master" was declared as offensive.
A proposal was formalized for replacing the word "master" with
"control plane". This means it should be removed from source code,
documentation, and user-facing configuration from Kubernetes and
its sub-projects.
NOTE: The reason why this changes it to kube_control_plane not
kube-control-plane is for valid group names on ansible.
[1]: https://github.com/kubernetes/enhancements/blob/master/keps/sig-cluster-lifecycle/kubeadm/2067-rename-master-label-taint/README.md#motivation
34 lines
1.4 KiB
Markdown
34 lines
1.4 KiB
Markdown
# 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](/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`.
|