Planning and managing your cloud ecosystem and environments is vital for decreasing manufacturing downtime and sustaining a functioning workload. Within the “Managing your cloud ecosystems” weblog collection, we cowl totally different methods for making certain that your setup capabilities easily with minimal downtime.
To begin issues off, the primary matter on this weblog collection is making certain workload continuity throughout employee node upgrades.
What are employee node upgrades?
Employee node upgrades apply essential safety updates and patches and must be accomplished often. For extra info 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 change into unavailable. It’s essential 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 utility downtime will permit you to simply apply employee node upgrades often.
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 may also use labels to use totally different guidelines to totally different employee nodes. For full directions, see Updating Classic worker nodes in the CLI with a configmap within the Kubernetes service documentation. If you happen to select to not create a configmap, the default most quantity of employee nodes that change into unavailable is 20%.
If you happen to want your complete variety of employee nodes to stay up and working, use the ibmcloud ks worker-pool resize command to quickly add additional employee nodes to your cluster throughout 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 measurement.
For VPC employee nodes
VPC employee nodes are changed by eradicating the previous 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 identical time, however in case you improve a number of without delay, they change into unavailable on the identical time. To be sure to have sufficient capability to run your workload throughout the improve, you may plan to both resize your worker pools to quickly add additional employee nodes (just like the method described for traditional employee nodes) or plan to improve your employee nodes one after the other.
Wrap up
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 will help you create a extra streamlined, environment friendly setup with restricted downtime.
Now that you’ve a plan to forestall disruptions throughout employee node upgrades, hold an eye fixed out for the subsequent weblog in our collection, which can talk about how, when and why to implement main, minor or patch upgrades to your clusters and employee nodes.
Learn more about IBM Cloud Kubernetes Service clusters
