IP Library Granted Patent US 12,608,191
Granted Patent B2
US 12,608,191 · App. 18/570,134 · Granted Apr 21, 2026

Update control method of container infrastructure cluster, update system of container infrastructure cluster, update control device, and update control program

Inventors: Kenta Shinohara (Musashino, JP); Noritaka Horikome (Musashino, JP); Takahiro Terayama (Musashino, JP); Masaki Ueno (Musashino, JP)
Assignee: NTT, Inc.
G06F8/65
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,608,191
App. No.
18/570,134
Granted
Apr 21, 2026
Kind
B2
Abstract

An update control device of a container-based cluster update system constructs a master node in a new container-based cluster and constructs a minimum number of worker nodes required to execute a migration target application. The update control device deletes a migration target application of a container-based cluster in an initial state, deletes a worker node in which no application is installed, adds the worker node to a new container-based cluster, and sequentially migrates the migration target application to perform update.

Claims (35)

1 . An update control method for a container-based cluster using a container-based cluster update system including a container-based cluster, an update control device configured to control update of the container-based cluster, and a load balancer, in which the container-based cluster includes a plurality of worker nodes that cause a virtualized container to execute processing of an application and a master node configured to manage the worker nodes, one or more of the applications being made redundant in the plurality of worker nodes, and the redundant applications being installed in different worker nodes, the update control method comprising:

a master node construction step of constructing a new master node in a new container-based cluster different from the container-based cluster in an initial state before update;

a worker node construction step of constructing, in the new container-based cluster, a minimum number of the worker nodes required for a migration target application to execute processing, the migration target application being selected from among the one or more applications installed in the plurality of worker nodes of the container-based cluster in the initial state and indicating an application that is a target to be sequentially migrated to the new container-based cluster;

an application installation step of installing the migration target application in the minimum required number of the constructed worker nodes;

a communication connection step of communicatively connecting the worker node in which the migration target application is installed and the load balancer;

an application deletion step of deleting the migration target application from the container-based cluster in the initial state;

a worker node deletion step of deleting a worker node in which the application is no longer installed due to the deletion of the migration target application from the container-based cluster in the initial state; and

a worker node addition step of adding the number of worker nodes deleted from the container-based cluster in the initial state to the new container-based cluster, wherein

the update control device is configured to:

sequentially select the migration target application in the container-based cluster in the initial state to install the migration target application in a worker node constructed in the new container-based cluster, repeat deletion of the migration target application from the container-based cluster in the initial state and deletion of a worker node in which the application is not installed to migrate all applications, and delete the master node of the container-based cluster in the initial state to update the container-based cluster in the initial state to the new container-based cluster, and

in each of the steps, check whether or not each of the steps has been executed normally by inquiring the master node of the container-based cluster in the initial state or the new container-based cluster, and in a case where there is a step that has not been executed normally, return processing to immediately before the step, and execute the step again.

2 . The update control method for a container-based cluster according to claim 1 , wherein in the worker node deletion step, in a case where there is no worker node in which the application is no longer installed, the update control device is configured to move an application installed in one of the worker nodes to another worker node and generate a worker node in which the application is no longer installed.

3 . A container-based cluster update system comprising:

a container-based cluster;

an update control device configured to control update of the container-based cluster; and

a load balancer, wherein

the container-based cluster includes a plurality of worker nodes that cause a virtualized container to execute processing of an application and a master node configured to manage the worker nodes, one or more of the applications being made redundant in the plurality of worker nodes, and the redundant applications being installed in different worker nodes,

the update control device includes

a master node control unit, comprising one or more processors, configured to construct a new master node in a new container-based cluster different from the container-based cluster in an initial state before update,

a worker node control unit, comprising one or more processors, configured to construct, in the new container-based cluster, a minimum number of the worker nodes required for a migration target application to execute processing, the migration target application being selected from among the one or more applications installed in the plurality of worker nodes of the container-based cluster in the initial state and indicating an application that is a target to be sequentially migrated to the new container-based cluster, and that delete a worker node in which the application is no longer installed due to deletion of the migration target application from the container-based cluster in the initial state, and add the number of deleted worker nodes to the new container-based cluster,

an application management unit, comprising one or more processors, configured to install the migration target application in the minimum required number of constructed worker nodes and delete the migration target application from the container-based cluster in the initial state,

a load balancer control unit, comprising one or more processors, configured to communicatively connect the worker node in which the migration target application is installed and the load balancer, and

a state acquisition unit, comprising one or more processors, configured to inquire the master node of the container-based cluster in the initial state or the new container-based cluster to check normality of each process related to update, and

the update control device is configured to:

sequentially select the migration target application in the container-based cluster in the initial state to cause the application management unit to install the migration target application in a worker node of the new container-based cluster constructed by the worker node control unit, repeat deletion of the migration target application from the container-based cluster in the initial state in the application management unit and deletion of a worker node in which the application is not installed in the worker node control unit to migrate all applications, and delete the master node of the container-based cluster in the initial state in the master node control unit to update the container-based cluster in the initial state to the new container-based cluster, and

in a case where there is a process of which normality cannot be checked as a result of checking the normality in the state acquisition unit, return to immediately before the process and execute the process again.

4 . An update control device configured to control update of a container-based cluster including a plurality of worker nodes that cause a virtualized container to execute processing of an application and a master node configured to manage the worker nodes, one or more of the applications being made redundant in the plurality of worker nodes, and the redundant applications being installed in different worker nodes, the update control device comprising:

a master node control unit, comprising one or more processors, configured to construct a new master node in a new container-based cluster different from the container-based cluster in an initial state before update;

a worker node control unit, comprising one or more processors, configured to construct, in the new container-based cluster, a minimum number of the worker nodes required for a migration target application to execute processing, the migration target application being selected from among the one or more applications installed in the plurality of worker nodes of the container-based cluster in the initial state and indicating an application that is a target to be sequentially migrated to the new container-based cluster, and delete a worker node in which the application is no longer installed due to deletion of the migration target application from the container-based cluster in the initial state, and add the number of deleted worker nodes to the new container-based cluster;

an application management unit, comprising one or more processors, configured to install the migration target application in the minimum required number of constructed worker nodes and delete the migration target application from the container-based cluster in the initial state,

a load balancer control unit, comprising one or more processors, configured to communicatively connect the worker node in which the migration target application is installed and the load balancer configured to allocate a processing request to each of the applications; and

a state acquisition unit, comprising one or more processors, configured to inquire the master node of the container-based cluster in the initial state or the new container-based cluster to check normality of each process related to update, wherein

the update control device is configured to:

sequentially select the migration target application in the container-based cluster in the initial state to cause the application management unit to install the migration target application in a worker node of the new container-based cluster constructed by the worker node control unit, repeat deletion of the migration target application from the container-based cluster in the initial state in the application management unit and deletion of a worker node in which the application is not installed in the worker node control unit to migrate all applications, and delete the master node of the container-based cluster in the initial state in the master node control unit to update the container-based cluster in the initial state to the new container-based cluster, and

in a case where there is a process of which normality cannot be checked as a result of checking the normality in the state acquisition unit, return to immediately before the process and execute the process again.

Assignments (3)
CHANGE OF NAME Recorded Aug 14, 2025
From: NIPPON TELEGRAPH AND TELEPHONE CORPORATION
To: NTT, INC.
Reel/Frame 072460/0605 →
CHANGE OF NAME Recorded Aug 14, 2025
From: NIPPON TELEGRAPH AND TELEPHONE CORPORATION
To: NTT, INC.
Reel/Frame 073460/0980 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 14, 2023
From: SHINOHARA, KENTA; HORIKOME, NORITAKA; TERAYAMA, TAKAHIRO; UENO, MASAKI
To: NIPPON TELEGRAPH AND TELEPHONE CORPORATION
Reel/Frame 065875/0556 →
Continuity (1)
Related Publication 20240281242A1 · Aug 22, 2024
References Cited (13)
US 11469944B1 · Lindholm · 2022 [cited by examiner]
US 12160340B2 · Erez · 2024 [cited by examiner]
US 20190050296A1 · Luo · 2019 [cited by examiner]
US 20190324785A1 · Weissman · 2019 [cited by examiner]
US 20200153898A1 · Sabath · 2020 [cited by examiner]
US 20210279111A1 · Ranjan · 2021 [cited by examiner]
US 20220075613A1 · Ramachandran · 2022 [cited by examiner]
US 20220114004A1 · Hsu · 2022 [cited by examiner]
US 20220229687A1 · Singhal · 2022 [cited by examiner]
CN 113704029A · 2021 [cited by examiner]
Be-ars.colopl.co.jp [online], “How ‘Dragon Quest Walk’ adopted a Kubernetes multi-cluster configuration,” available on Jan. 2021, retrieved on Jan. 2021, retrieved from URL<https://be-ars.colopl.co.jp/team/en-blog_vol6.… [cited by applicant]
Kubernetes.io [online], “Performing Rolling Updates,” available on or before Jun. 2019, retrieved on Oct. 2023, retrieved from URL<https://kubernetes.io/ja/docs/tutorials/kubernetes-basics/update/update-intro/>, 5 pages… [cited by applicant]
Redhat.com [online], “What is blue-green deployment?”, available on Jun. 2019, retrieved on Jun. 2021, retrieved from URL<https://www.redhat.com/ja/topics/devops/what-is-blue-green-deployment>, 15 pages (with machine tr… [cited by applicant]