Container Management Node Update Without Service Interruption
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing rolling update methods in container management platforms disrupt business operations during management node updates, as they require stopping API services, preventing business processing and resource expansion, which can lead to adverse service effects.
Innovation Solution
An update device that transfers execution nodes from one management node to another, allowing business processing to continue during management node updates by separating the execution node from the cluster and transferring its management to another node, enabling updates without interrupting service operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If rolling update is adopted for management nodes, then update efficiency is improved, but business operations are interrupted
Solution Approach 1:
The system segments the cluster into multiple management nodes (first management node and second management node) and separates execution nodes into different groups. This allows one management node to be updated while the other continues to handle business operations, thus maintaining service continuity during updates.
Solution Approach 2:
The load balancer acts as an intermediary to redirect traffic away from the first cluster during its management node update. The transfer unit serves as a mediator to transfer execution nodes from the first management node to the second management node, ensuring business operations continue without interruption.
2Stability of the object's composition
If management nodes are updated one at a time, then system stability is maintained, but update time is extended
Solution Approach 1:
The cluster is segmented into multiple management nodes that can be updated in parallel. The first management node and second management node operate independently, allowing simultaneous updates while maintaining system stability through the presence of at least one operational management node.
Solution Approach 2:
The transfer unit transfers execution nodes to the second management node before the first management node is fully updated. This preliminary action ensures that business operations are already migrated to the second management node, reducing the overall update time while maintaining stability.
3Reliability
If execution nodes are transferred between management nodes, then business continuity is maintained, but system complexity increases
Solution Approach 1:
Both the first management node and second management node are configured with identical functionality to manage execution nodes. This universality allows execution nodes to be transferred between management nodes without requiring different system configurations, simplifying the transfer mechanism while maintaining business continuity.
Solution Approach 2:
The update unit monitors the status of management nodes and automatically triggers execution node transfers when needed. This feedback mechanism ensures that transfers occur only when necessary (when a management node is being updated), maintaining business continuity without requiring complex manual intervention.
Data Source
AI summary
Provided is an update device capable of appropriately updating the nodes used in business processing. The update device comprises a communication control unit which instructs the load balancer to stop distribution to the first cluster, a transfer unit which instructs the first management node and the second management node to transfer the first execution node from being under management of the first management node to being under management of the second management node, and an update unit which instructs the first management node to update the first management node on grounds that the first execution node being under management of the first management node has been transferred to being under management of the second management node.