Worker Node Migration via Dual Communication Pathway Switching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Service providers face challenges in seamlessly migrating or updating clusters in a virtual cloud network without disrupting customer services, particularly when components are deployed across multiple tenancies, as they lack direct access to customer tenancy components.
Innovation Solution
The method involves switching network communications between worker nodes and manager instances by creating new communication pathways, updating IP addresses, and using existing components like DaemonSets and software-defined virtual network interfaces to disconnect and reconnect components, allowing for migration or update without direct access to customer tenancy components.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If service providers directly access customer tenancy components to perform migration or update operations, then the migration process can be directly controlled and managed, but customer security and tenancy isolation are compromised
Solution Approach 1:
The patent introduces an intermediary mechanism where the service provider creates a new manager instance that acts as a mediator between the worker nodes and the target manager instance. The container tool on worker nodes communicates with the new manager instance, which then manages the transition to the target manager instance. This intermediary approach allows the service provider to control the migration process while maintaining security boundaries, as the new manager instance is created within the customer's tenancy and handles all communications securely.
2Adaptability or versatility
If the migration process disrupts network communications between worker nodes and manager instances, then the update can be performed, but service continuity is interrupted
Solution Approach 1:
The patent implements preliminary action by creating the new manager instance and establishing its communication pathways before the old manager instance is decommissioned. The container tool on worker nodes is updated to use the new manager instance's IP address while the old instance is still operational. This allows the migration to proceed without interrupting service, as the transition is prepared in advance and executed smoothly.
Solution Approach 2:
The patent ensures continuity of useful action by maintaining network communications throughout the migration process. The new manager instance is created with IP addresses that are integrated into the existing network fabric, allowing worker nodes to continue communicating without interruption. The old manager instance remains operational during the transition, providing a fallback path and ensuring that service continuity is maintained until the migration is complete.
3Reliability
If multiple communication pathways are maintained during migration, then service continuity is preserved, but network complexity increases
Solution Approach 1:
The patent applies segmentation by dividing the migration process into distinct phases with clearly defined communication pathways. The first pathway is from worker nodes to the new manager instance, and the second pathway is from the new manager instance to the target manager instance. This segmentation allows each pathway to be managed independently, reducing the overall complexity despite maintaining multiple pathways during transition.
Data Source
AI summary
Techniques for migrating worker nodes within clusters to a new manager instance. One technique includes receiving a request to migrate or update a configuration of a cluster within a container system, where the migration or update includes switching from a first communication pathway to a second communication pathway between worker nodes and a manager instance; creating a component and associated IP address for the second communication pathway; communicating a pod specification that includes the IP address for the second communication pathway to the manager instance, where the pod specification will cause a container tool to update each of the worker nodes with the IP address for the second communication pathway; receiving a notification that all worker nodes have been updated with the IP address; and removing a component and associated IP address for the first communication pathway from the cluster.