Cloud-independent node upgrade
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.
1 . A computer system for upgrading one or more container nodes 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 having an outdated server instance configuration;
identify for an upgrade one or more container nodes associated with the cloud-based server instance, wherein the one or more container nodes identified for the upgrade belong to a cluster and the upgrade of the one or more container nodes identified for the upgrade is prioritized based on the one or more container nodes identified for the upgrade being non-visible with respect to other container nodes within the cluster;
upgrade the one or more container nodes identified for the upgrade by instantiating one or more replacement container nodes having a pre-determined upgrade configuration associated with a new version identifier;
associate the new version identifier with the cloud-based server instance and the one or more replacement container nodes; and
mark for termination the one or more container nodes identified for the upgrade.
2 . The system of claim 1 , wherein the processor is configured to associate the new version identifier into a map tracking a plurality of version identifiers, a plurality of cloud-based server instances, and a plurality of non-visible container nodes.
3 . 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 the one or more non-visible container nodes configured on each cloud-based server instance of the subset and one or more container deployment units associated with each identified non-visible container node;
prepare the identified one or more non-visible container nodes for upgrade; and
migrate the one or more container deployment units to one of the replacement container nodes.
4 . The system of claim 3 , 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.
5 . The system of claim 4 , wherein the processor is configured to select the subset of cloud-based server instances based on a visibility of the identified one or more non-visible container nodes configured on each cloud-based server instance.
6 . The system of claim 1 , wherein the system is operable outside a container cluster of the one or more container nodes.
7 . 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.
8 . A method for upgrading one or more container nodes in a cloud environment, the method comprising:
obtaining a version identifier associated with a cloud-based server instance having an outdated server instance configuration;
identifying for upgrade the one or more container nodes associated with the cloud-based server instance, wherein the one or more container nodes identified for the upgrade belong to a cluster and the upgrade of the one or more container nodes identified for the upgrade is prioritized based on the one or more container nodes identified for the upgrade being non-visible with respect to other container nodes within the cluster;
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, wherein the upgrading the one or more container nodes further comprises upgrading a configuration for the cloud-based server instance;
selecting a subset of cloud-based server instances for upgrading based on a visibility of the one or more container nodes configured on each cloud-based server instance; and
associating the new version identifier with the cloud-based server instance and the one or more replacement container nodes, and marking for termination the one or more container nodes.
9 . The method of claim 8 , 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.
10 . The method of claim 9 , 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.
11 . The method of claim 9 , wherein the one or more child objects comprise one or more container deployment units.
12 . The method of claim 9 , wherein the one or more child objects comprise one or more Kubernetes pods.
13 . The method of claim 8 , wherein the one or more container nodes are operable on a plurality of cloud environments.
14 . The method of claim 8 , wherein the one or more replacement container nodes are operable on a plurality of cloud environments.
15 . The method of claim 8 , 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.
16 . The method of claim 8 , 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.
17 . The method of claim 8 , wherein the cloud-based server instance comprises an Elastic Cloud Computing instance.
18 . The method of claim 8 , wherein the cloud-based server instance belongs to an Auto Scaling Group.
19 . The method of claim 8 , wherein the one or more container nodes comprise one or more Kubernetes worker nodes.