# US 2022/0035626 A1 · Cloud-independent node upgrade

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0035626 A1
- Document ID: US20220035626A1
- Status: Published application
- Kind: A1
- Application number: 17/139,267
- Filed: 2020-12-31
- Published: 2022-02-03
- Earliest claimed: 2020-07-31
- Assignees: Pegasystems Inc.
- Applicants: Pegasystems Inc.
- Inventors: Karan Kapoor; Abirami Natarajan; Kevin Lee Walsh
- Web page: https://patentgrep.com/patent/US20220035626A1

## CPC

- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F 8/656: while running
- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- G06F 8/71: Version control (security arrangements therefor G06F21/57); Configuration management
- G06F 2009/45562: {Creating, deleting, cloning virtual machine instances}
- G06F 2009/45575: {Starting, stopping, suspending or resuming virtual machine instances}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems, methods, and computer program products are disclosed for upgrading a container node in a cloud environment. The system includes a processor coupled to a memory and a network interface. The processor is configured to obtain a version identifier associated with a cloud-based server instance and one or more container nodes operable in a cloud environment. The processor is further configured to identify the one or more container nodes associated with the cloud-based server instance. The processor is further configured to upgrade the one or more container nodes by instantiating one or more replacement container nodes having a pre-determined upgrade configuration associated with a new version identifier. The processor is further configured to associate the new version identifier with the cloud-based server instance and the one or more replacement container nodes.

## Claims

### Claim 1

A computer system for upgrading a container node in a cloud environment, the system comprising:
a processor coupled to a memory and a network interface, wherein the processor is configured to:
obtain a version identifier associated with a cloud-based server instance and one or more container nodes operable in a cloud environment;
identify the one or more container nodes associated with the cloud-based server instance;
upgrade the one or more container nodes by instantiating one or more replacement container nodes having a pre-determined upgrade configuration associated with a new version identifier; and
associate the new version identifier with the cloud-based server instance and the one or more replacement container nodes.

### Claim 2 (depends on 1)

The system of claim 1, wherein the processor is configured to obtain the version identifier from a map tracking a plurality of version identifiers, a plurality of cloud-based server instances, and a plurality of container nodes.

### Claim 3 (depends on 1)

The system of claim 1, wherein the processor is configured to associate the new version identifier into a map tracking the plurality of version identifiers, the plurality of cloud-based server instances, and the plurality of container nodes.

### Claim 4 (depends on 1)

The system of claim 1, wherein the processor configured to upgrade the one or more container nodes comprises the processor being further configured to:
upgrade a configuration for the cloud-based server instance;
select a subset of cloud-based server instances for upgrading;
identify one or more container nodes configured on each cloud-based server instance of the subset and one or more container deployment units associated with each identified container node;
prepare the identified container nodes for upgrade; and
migrate the one or more container deployment units to one of the replacement container nodes.

### Claim 5 (depends on 4)

The system of claim 4, wherein the processor configured to upgrade the configuration for the cloud-based server instance comprises the processor being further configured to provision an updated configuration for the cloud-based server instance.

### Claim 6 (depends on 5)

The system of claim 5, wherein the processor is configured to select the subset of cloud-based server instances based on a visibility of the one or more container nodes configured on each cloud-based server instance.

### Claim 7 (depends on 1)

The system of claim 1, wherein the system is operable outside a container cluster of the one or more container nodes.

### Claim 8 (depends on 1)

The system of claim 1, wherein the system is operable in a control plane of a container cluster of the one or more container nodes.

### Claim 9

A method for upgrading a container node in a cloud environment, the method comprising:
obtaining a version identifier associated with a cloud-based server instance and one or more container nodes operable in a cloud environment;
identifying the one or more container nodes associated with the cloud-based server instance;
upgrading the one or more container nodes by instantiating one or more replacement container nodes having a pre-determined upgrade configuration associated with a new version identifier; and
associating the new version identifier with the cloud-based server instance and the one or more replacement container nodes.

### Claim 10 (depends on 9)

The method of claim 9, wherein the upgrading the one or more container nodes further comprises identifying one or more child objects associated with the one or more container nodes.

### Claim 11 (depends on 10)

The method of claim 10, wherein the upgrading the one or more container nodes further comprises migrating the one or more child objects to the one or more replacement container nodes.

### Claim 12 (depends on 10)

The method of claim 10, wherein the one or more child objects comprise one or more container deployment units.

### Claim 13 (depends on 10)

The method of claim 10, wherein the one or more child objects comprise one or more Kubernetes pods.

### Claim 14 (depends on 9)

The method of claim 9, wherein the one or more container nodes are operable on a plurality of cloud environments.

### Claim 15 (depends on 9)

The method of claim 9, wherein the one or more replacement container nodes are operable on a plurality of cloud environments.

### Claim 16 (depends on 9)

The method of claim 9, wherein the one or more replacement container nodes are operable on a cloud environment that is different from the cloud environment on which the one or more container nodes are operable.

### Claim 17 (depends on 9)

The method of claim 9, wherein the upgrading the one or more container nodes further comprises instantiating the one or more replacement container nodes on a new cloud-based server instance that is operable on a different cloud infrastructure from the initial cloud-based server instance.

### Claim 18 (depends on 9)

The method of claim 9, wherein the cloud-based server instance comprises an Elastic Cloud Computing instance.

### Claim 19 (depends on 9)

The method of claim 9, wherein the cloud-based server instance belongs to an Auto Scaling Group.

### Claim 20 (depends on 9)

The method of claim 9, wherein the one or more container nodes comprise one or more Kubernetes worker nodes.
