
Add documentation about "hybrid clusters" where there are a mix of Kubernetes and OpenStack nodes in the same cluster. Add documentation about converting worker nodes to compute nodes. Removed new content from r5 as it was not relevant. Fixed typos. New step added in Convert Worker Nodes section. Signed-off-by: Elisamara Aoki Goncalves <elisamaraaoki.goncalves@windriver.com> Change-Id: Ie39bc8b94e2281649a26b13ceb778325ff53422e
1.7 KiB
1.7 KiB
Hybrid Cluster
A Hybrid Cluster occurs when the hosts with a worker function ( controllers and worker nodes) are split between two groups, one running for hosting payloads and the other for hosting containerized payloads.
The host labels are used to define each worker function on the Hybrid Cluster setup. For example, a standard configuration (2 controllers and 2 computes) can be split into (2 controllers, 1 openstack-compute and 1 kubernetes-worker).
Limitations
- Worker function on controllers MUST both be either Kubernetes or
OpenStack.
- Hybrid Cluster does not apply to or setups.
- A worker must have only one function, either it is OpenStack compute
or k8s-only worker, never both at the same time.
- The
sriov
andsriovdp
labels cannot coexist on the same host, in order to prevent the device plugin from conflicting with the OpenStack driver. - No host will assign and application containers to application cores at the same time.
- The
- Standard Controllers cannot have
openstack-compute-node
label; only Controllers can haveopenstack-compute-node
label. - Taints must be added to OpenStack compute hosts (i.e. worker nodes
or -Controller nodes with the
openstack-compute-node
label) to prevent end users' hosted containerized workloads/pods from being scheduled on OpenStack compute hosts. SeeAdd Taints to OpenStack Node in Hybrid Cluster <add-taints-to-openstack-node-in-hybrid-cluster-e8b37e8d1b48-r6>
.