Propagating fault domain topology to nodes in a distributed container orchestration system
An example method of propagating fault domain topology information in a distributed container orchestration system includes: receiving, at control plane software executing in a data center, the fault domain topology, which includes tags for a protection group and fault domains for remote sites in communication with the data center; deploying, by a master server of the distributed container orchestration system that executes in the data center, a node pool comprising virtual machines (VMs) executing in servers of the remote sites, the VMs being nodes of the distributed container orchestration system in which containers execute; determining, by a controller of the master server, relationships among the VMs, the servers, the protection group, and the fault domains based on state of resources maintained by the master server; and providing, by the controller, labels to the servers for associating the tags of the protection group and the fault domains to the VMs.
1. A method of propagating a fault domain topology in a distributed container orchestration system, comprising:
receiving, at control plane software executing in a data center, the fault domain topology, which includes tags for a protection group and fault domains for remote sites in communication with the data center;
deploying, by a master server of the distributed container orchestration system that executes in the data center, a node pool comprising virtual machines (VMs) executing in servers of the remote sites, the VMs being nodes of the distributed container orchestration system in which containers execute;
determining, by a controller of the master server, relationships among the VMs, the servers, the protection group, and the fault domains based on state of resources maintained by the master server; and
providing, by the controller, labels to the servers for associating the tags of the protection group and the fault domains to the VMs.
2. The method of claim 1 , wherein the resources maintained by the master server include first resources that relate the tags of the protection group and the fault domains to the servers of the remote sites, and second resources that relate the VMs to the servers in which the VMs execute.
3. The method of claim 2 , wherein the control plane software interacts with the master server to create the first resources in response to creation of the fault domain topology.
4. The method of claim 2 , wherein a system controller of the master server creates the second resources in response to deployment of the node pool.
5. The method of claim 1 , further comprising:
updating, by the controller, the labels in response to a change in the state of the resources maintained by the master server.
6. The method of claim 1 , wherein the labels are added to configuration files for the VMs.
7. The method of claim 1 , wherein a high availability (HA) system is configured to read the labels when performing an HA operation in the node pool.
8. A non-transitory computer readable medium comprising instructions to be executed in a computing device to cause the computing device to carry out a method of propagating a fault domain topology in a distributed container orchestration system, comprising:
receiving, at control plane software executing in a data center, the fault domain topology, which includes tags for a protection group and fault domains for remote sites in communication with the data center;
deploying, by a master server of the distributed container orchestration system that executes in the data center, a node pool comprising virtual machines (VMs) executing in servers of the remote sites, the VMs being nodes of the distributed container orchestration system in which containers execute;
determining, by a controller of the master server, relationships among the VMs, the servers, the protection group, and the fault domains based on state of resources maintained by the master server; and
providing, by the controller, labels to the servers for associating the tags of the protection group and the fault domains to the VMs.
9. The non-transitory computer readable medium of claim 8 , wherein the resources maintained by the master server include first resources that relate the tags of the protection group and the fault domains to the servers of the remote sites, and second resources that relate the VMs to the servers in which the VMs execute.
10. The non-transitory computer readable medium of claim 9 , wherein the control plane software interacts with the master server to create the first resources in response to creation of the fault domain topology.
11. The non-transitory computer readable medium of claim 9 , wherein a system controller of the master server creates the second resources in response to deployment of the node pool.
12. The non-transitory computer readable medium of claim 8 , further comprising:
updating, by the controller, the labels in response to a change in the state of the resources maintained by the master server.
13. The non-transitory computer readable medium of claim 8 , wherein the labels are added to configuration files for the VMs.
14. The non-transitory computer readable medium of claim 8 , wherein a high availability (HA) system is configured to read the labels when performing an HA operation in the node pool.
15. A virtualized computing system, comprising:
a data center in communication with remote sites over a network forming a distributed container orchestration system; and
software executing in the data center, the software configured to:
receive, at control plane software executing in the data center, a fault domain topology, which includes tags for a protection group and fault domains for the remote sites;
deploy, by a master server of the distributed container orchestration system that executes in the data center, a node pool comprising virtual machines (VMs) executing in servers of the remote sites, the VMs being nodes of the distributed container orchestration system in which containers execute;
determine, by a controller of the master server, relationships among the VMs, the servers, the protection group, and the fault domains based on state of resources maintained by the master server; and
provide, by the controller, labels to the servers for associating the tags of the protection group and the fault domains to the VMs.
16. The virtualized computing system of claim 15 , wherein the resources maintained by the master server include first resources that relate the tags of the protection group and the fault domains to the servers of the remote sites, and second resources that relate the VMs to the servers in which the VMs execute.
17. The virtualized computing system of claim 16 , wherein the control plane software interacts with the master server to create the first resources in response to creation of the fault domain topology.
18. The virtualized computing system of claim 16 , wherein a system controller of the master server creates the second resources in response to deployment of the node pool.
19. The virtualized computing system of claim 15 , wherein the labels are added to configuration files for the VMs.
20. The virtualized computing system of claim 15 , wherein a high availability (HA) system is configured to read the labels when performing an HA operation in the node pool.