Statefulsets graceful termination for cloud computing platforms

A computer-program product tangibly embodied in one or more non-transitory machine-readable storage media, including instructions configured to cause a computing system to perform a set of actions comprising:

• identifying, using a cloud orchestration platform, a data set that is to be associated with a given client, wherein the data set corresponds to one or more task processes associated with a microservice;
• identifying a set of pods that includes a master pod and one or more worker pods, wherein the master pod is to be assigned to managing the one or more task processes corresponding to the data set, wherein each of the set of pods corresponds to a code-execution unit and was generated via the cloud orchestration platform, and wherein each of the one or more worker pods replicates data from the master pod;
• accessing the master pod by calling a container orchestration platform;
• detecting that an input triggers an upgrade for at least part of the master pod and at least part of each of the one or more worker pods has been received;
• and
• in response to detecting the trigger:
• interrupting a default pod-replacement protocol of the container orchestration platform by transmitting a custom script, from the cloud orchestration platform to the container orchestration platform, wherein the custom script includes specifications for the container orchestration platform to:
• poll the microservice for status information of the master pod and at least one of the one or more worker pods;
• and
• determine whether a condition for iteration advancement for the upgrade is satisfied based on the status information;
• and
• initiating an iteration advancement of the upgrade to a next pod of the set of pods upon determining that the condition for iteration advancement for the upgrade is satisfied.

A system comprising:

• one or more data processors;
• and
• one or more non-transitory computer readable storage media containing instructions which, when executed on the one or more data processors, cause the system to perform a set of actions comprising:
• identifying, using a cloud orchestration platform, a data set that is to be associated with a given client, wherein the data set corresponds to one or more task processes associated with a microservice;
• identifying a set of pods that includes a master pod and one or more worker pods, wherein the master pod is to be assigned to managing the one or more task processes corresponding to the data set, wherein each of the set of pods corresponds to a code-execution unit and was generated via the cloud orchestration platform, and wherein each of the one or more worker pods replicates data from the master pod;
• accessing the master pod by calling a container orchestration platform;
• detecting that an input triggers an upgrade for at least part of the master pod and at least part of each of the one or more worker pods has been received;
• and
• in response to detecting the trigger:
• interrupting a default pod-replacement protocol of the container orchestration platform by transmitting a custom script, from the cloud orchestration platform to the container orchestration platform, wherein the custom script includes specifications for the container orchestration platform to:
• poll the microservice for status information of the master pod and at least one of the one or more worker pods;
• and
• determine whether a condition for iteration advancement for the upgrade is satisfied based on the status information;
• and
• initiating an iteration advancement of the upgrade to a next pod of the set of pods upon determining that the condition for iteration advancement for the upgrade is satisfied.