Node pool cycling with boot volume replacement

A service provider computing system comprising:

• one or more memories;
• and
• one or more processors in communication with the one or more memories and configured to execute instructions stored in the one or more memories to perform operations comprising:
• receiving, from a data store, a first request that comprises a node identifier identifying a node executing as part of one or more containerized applications, wherein the first request indicates that a configuration of the node is to be updated to an updated configuration;
• determining whether the configuration is different from the updated configuration;
• in accordance with determining the configuration is different:
• transmitting a second request including the node identifier and requesting the node be cordoned to an application programming interface (API) server;
• transmitting a third request comprising the node identifier and requesting the node be drained to the API server;
• transmitting a fourth request to replace a boot volume of the node to a compute service;
• associating the updated configuration with the node;
• in accordance with receiving a response from the compute service based at least in part on the fourth request:
• transmitting a fifth request comprising the node identifier and requesting the node be uncordoned to the API server;
• and
• transmitting a status indicator to the data store to indicate that the first request was successful.

A non-transitory computer-readable medium storing a plurality of instructions that, when executed by one or more processors of a service provider computing system, cause the one or more processors to perform operations comprising:

• receiving, from a data store, a first request that comprises a node identifier identifying a node executing as part of one or more containerized applications, wherein the first request indicates that a configuration of the node is to be updated to an updated configuration;
• determining whether the configuration is different from the updated configuration;
• in accordance with determining the configuration is different:
• transmitting a second request including the node identifier and requesting the node be cordoned to an application programming interface (API) server;
• transmitting a third request comprising the node identifier and requesting the node be drained to the API server;
• transmitting a fourth request to replace a boot volume of the node to a compute service;
• associating the updated configuration with the node;
• in accordance with receiving a response from the compute service based at least in part on the fourth request:
• transmitting a fifth request comprising the node identifier and requesting the node be uncordoned to the API server;
• and
• transmitting a status indicator to the data store to indicate that the first request was successful.