Automated Fault Domain Topology Propagation in Kubernetes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In Kubernetes-based radio access network deployments, manually labeling fault domain topology for each node is labor-intensive and error-prone, especially in large-scale setups, which can lead to inconsistencies and affect high availability.
Innovation Solution
A method to propagate fault domain topology information automatically by receiving and processing tags for protection groups and fault domains at the control plane software, determining relationships among VMs, servers, and protection groups, and providing labels to VMs for accurate association, thereby eliminating the need for manual tagging.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If manual labeling of fault domain topology is performed for each node, then accuracy of fault domain information can be maintained, but labor intensity and time consumption increase significantly
Solution Approach 1:
The patent automatically copies fault domain topology information from infrastructure resources (servers, sites, zones) to container orchestration nodes by establishing correspondence relationships. Instead of manually creating labels for each node, the system automatically generates and propagates fault domain labels based on the underlying infrastructure topology, thereby maintaining accuracy while eliminating manual labeling time consumption.
Solution Approach 2:
The system enables self-service by allowing the container orchestration platform to automatically determine and assign fault domain labels to nodes based on infrastructure information. The fault domain topology propagation mechanism automatically queries infrastructure resources, establishes relationships, and applies labels without human intervention, making the system self-configuring and eliminating manual operational overhead.
2Reliability
If manual labeling is performed for large-scale deployments, then fault domain topology can be established, but error rate increases due to manual intensity
Solution Approach 1:
By copying fault domain information automatically from infrastructure resources to container orchestration nodes through established correspondence relationships, the system eliminates manual labeling operations that are error-prone. The automatic propagation ensures consistency and accuracy across all nodes without human intervention, thereby improving reliability and eliminating labeling errors.
Solution Approach 2:
The system implements feedback mechanisms where the container orchestration platform continuously queries infrastructure resources to obtain current fault domain information and automatically updates node labels accordingly. This feedback loop ensures that fault domain topology remains consistent with the actual infrastructure state, preventing errors from divergent manual configurations.
3Productivity
If automatic propagation of fault domain topology is implemented, then labor intensity is reduced, but system complexity increases
Solution Approach 1:
The patent introduces an intermediary mechanism in the form of correspondence relationships between infrastructure resources and container orchestration nodes. This intermediary layer automatically maps infrastructure fault domain information to node labels, simplifying the propagation process. Instead of complex direct mapping, the intermediary correspondence relationships provide a structured, automated pathway that reduces system complexity while maintaining high productivity.
4Measurement precision
If fault domain topology is manually updated when nodes are recreated, then accuracy is maintained, but operational overhead increases
Solution Approach 1:
The system enables self-service by automatically detecting when nodes are recreated and propagating the appropriate fault domain labels without human intervention. The automated propagation mechanism continuously queries infrastructure resources and applies labels based on current topology, maintaining accuracy while eliminating the operational burden of manual updates during node lifecycle events.
Solution Approach 2:
The system implements feedback mechanisms that monitor node lifecycle events and automatically trigger fault domain label propagation when nodes are recreated. This feedback loop ensures that newly created nodes receive correct fault domain labels automatically, maintaining measurement precision while improving ease of operation by eliminating manual update requirements.
Data Source
AI summary
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.