US 11,816,469 B2
Resolving the version mismatch problem when implementing a rolling update in an open-source platform for container orchestration
Hong Jun Tu, Beijing (CN); Wen Tao Zhang, Beijing (CN); Yang Yang, Beijing (CN); Yiwen Huang, Markham (CA); Ye Cui, Beijing (CN); Xiao Kai Dong, Beijing (CN); and Yu Chi Zhang, Beijing (CN)
Assigned to International Business Machines Corporation, Armonk, NY (US)
Filed by INTERNATIONAL BUSINESS MACHINES CORPORATION, Armonk, NY (US)
Filed on Sep. 22, 2021, as Appl. No. 17/448,357.
Prior Publication US 2023/0088858 A1, Mar. 23, 2023
Int. Cl. G06F 9/445 (2018.01); G06F 8/65 (2018.01); H04L 45/02 (2022.01)
CPC G06F 8/65 (2013.01) [H04L 45/02 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A processor-implemented method for container lifecycle management, the method comprising:
registering a topology for a plurality of deployments in a container orchestration platform;
detecting a rolling update of a deployment of the plurality of deployments, to a new version;
in response to determining that the deployment has one or more ongoing connections to one or more pods of one or more other deployments within the plurality of deployments, assuming ownership, via a version controller, of at least one previous version pod of the deployment, wherein the assuming removes the at least one previous version pod from the deployment;
creating network routing rules for the at least one previous version pod; and
while other pods of the deployment are updating to respective new versions via the rolling update, routing network packets to the at least one previous version pod based on the created network routing rules, wherein the at least one previous version pod coexists with the respective new versions of the other pods of the deployment.