Planning and managing your cloud ecosystem and environments is essential for lowering manufacturing downtime and sustaining a functioning workload. Within the “Managing your cloud ecosystems” weblog sequence, we cowl completely different methods for guaranteeing that your setup capabilities easily with minimal downtime.
To start out issues off, the primary subject on this weblog sequence is guaranteeing workload continuity throughout employee node upgrades.
What are employee node upgrades?
Employee node upgrades apply necessary safety updates and patches and needs to be accomplished commonly. For extra data on kinds of employee node upgrades, see Updating VPC worker nodes and Updating Classic worker nodes within the IBM Cloud Kubernetes Service documentation.
Throughout an improve, a few of your employee nodes might develop into unavailable. It’s necessary to ensure your cluster has sufficient capability to proceed working your workload all through the improve course of. Constructing a pipeline to replace your employee nodes with out inflicting software downtime will can help you simply apply employee node upgrades commonly.
For traditional employee nodes
Create a Kubernetes configmap that defines the utmost variety of employee nodes that may be unavailable at a time, together with throughout an improve. The utmost worth is specified as a share. You can too use labels to use completely different guidelines to completely different employee nodes. For full directions, see Updating Classic worker nodes in the CLI with a configmap within the Kubernetes service documentation. When you select to not create a configmap, the default most quantity of employee nodes that develop into unavailable is 20%.
When you want your complete variety of employee nodes to stay up and working, use the
ibmcloud ks worker-pool resize command to briefly add additional employee nodes to your cluster all through the improve course of. When the improve is full, use the identical command to take away the extra employee nodes and return your employee pool to its earlier dimension.
For VPC employee nodes
VPC employee nodes are changed by eradicating the outdated employee node and provisioning a brand new employee node that runs on the new model. You possibly can improve a number of employee nodes on the similar time, however when you improve a number of without delay, they develop into unavailable on the similar time. To be sure you have sufficient capability to run your workload in the course of the improve, you may plan to both resize your worker pools to briefly add additional employee nodes (just like the method described for traditional employee nodes) or plan to improve your employee nodes one after the other.
Whether or not you select to implement a configmap, resize your employee pool or improve parts one-by-one, making a workload continuity plan earlier than you improve your employee nodes can assist you create a extra streamlined, environment friendly setup with restricted downtime.
Now that you’ve got a plan to stop disruptions throughout employee node upgrades, preserve a watch out for the following weblog in our sequence, which is able to talk about how, when and why to implement main, minor or patch upgrades to your clusters and employee nodes.