Planning and managing your cloud ecosystem and environments is important for decreasing manufacturing downtime and sustaining a functioning workload. Within the “Managing your cloud ecosystems” weblog collection, we cowl completely different methods for guaranteeing that your setup capabilities easily with minimal downtime.
To start out issues off, the primary matter on this weblog collection is guaranteeing workload continuity throughout employee node upgrades.
What are employee node upgrades?
Employee node upgrades apply essential safety updates and patches and must be accomplished repeatedly. For extra info on kinds of employee node upgrades, see Updating VPC employee nodes and Updating Traditional employee nodes within the IBM Cloud Kubernetes Service documentation.
Throughout an improve, a few of your employee nodes might turn into unavailable. It’s essential to ensure your cluster has sufficient capability to proceed operating 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 repeatedly.
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. It’s also possible to use labels to use completely different guidelines to completely different employee nodes. For full directions, see Updating Traditional employee nodes within 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 turn into unavailable is 20%.
When you want your complete variety of employee nodes to stay up and operating, use the ibmcloud ks worker-pool resize command to briefly add further employee nodes to your cluster during 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 previous employee node and provisioning a brand new employee node that runs on the new model. You’ll be able to improve a number of employee nodes on the similar time, however when you improve a number of directly, they turn into unavailable on the similar time. To be sure to have sufficient capability to run your workload throughout the improve, you possibly can plan to both resize your employee swimming pools to briefly add further 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 may also help you create a extra streamlined, environment friendly setup with restricted downtime.
Now that you’ve got a plan to forestall disruptions throughout employee node upgrades, maintain a watch out for the subsequent weblog in our collection, which can focus on how, when and why to implement main, minor or patch upgrades to your clusters and employee nodes.
Be taught extra about IBM Cloud Kubernetes Service clusters
