c12s-kubespray/docs/test_cases.md

# 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`.
Add markdown CI (#5380) 2019-12-04 15:22:57 +00:00			`# Node Layouts`
Add synthetic scale deployment mode New deploy modes: scale, ha-scale, separate-scale Creates 200 fake hosts for deployment with fake hostvars. Useful for testing certificate generation and propagation to other master nodes. Updated test cases descriptions. 2017-02-13 11:13:28 +00:00
			There are four node layout types: `default`, `separate`, `ha`, and `scale`.

			`default` is a non-HA two nodes setup with one separate `kube-node`
Replace kube-master with kube_control_plane (#7256) 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 2021-03-24 00:26:05 +00:00			and the `etcd` group merged with the `kube_control_plane`.
Add synthetic scale deployment mode New deploy modes: scale, ha-scale, separate-scale Creates 200 fake hosts for deployment with fake hostvars. Useful for testing certificate generation and propagation to other master nodes. Updated test cases descriptions. 2017-02-13 11:13:28 +00:00
			`separate` layout is when there is only node of each type, which includes
Replace kube-master with kube_control_plane (#7256) 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 2021-03-24 00:26:05 +00:00			`a kube_control_plane, kube-node, and etcd cluster member.`
Add synthetic scale deployment mode New deploy modes: scale, ha-scale, separate-scale Creates 200 fake hosts for deployment with fake hostvars. Useful for testing certificate generation and propagation to other master nodes. Updated test cases descriptions. 2017-02-13 11:13:28 +00:00
			`ha` layout consists of two etcd nodes, two masters and a single worker node,
			`with role intersection.`

Update test-cases documentation (#6264) 2020-06-18 06:40:05 +00:00			`scale` layout can be combined with above layouts (`ha-scale`, `separate-scale`). It includes 200 fake hosts
Add synthetic scale deployment mode New deploy modes: scale, ha-scale, separate-scale Creates 200 fake hosts for deployment with fake hostvars. Useful for testing certificate generation and propagation to other master nodes. Updated test cases descriptions. 2017-02-13 11:13:28 +00:00			`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.`
Improve CI test matrix For Travis CI and GCE, add a naive generator script into a markdown table. Add GCE/Travis CI matrix docs. Add CoreOS test cases. Rework existing cases w/o loosing of coverage. Rework postinstall tests to support CoreOS as well. Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com> 2016-11-15 17:17:30 +00:00
			`Note, the canal network plugin deploys flannel as well plus calico policy controller.`

Update test-cases documentation (#6264) 2020-06-18 06:40:05 +00:00			`## Test cases`

Fix some doc links (#6328) 2020-06-25 18:56:37 +00:00			`The [CI Matrix](/docs/ci.md) displays OS, Network Plugin and Container Manager tested.`
Update test-cases documentation (#6264) 2020-06-18 06:40:05 +00:00
			`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`.