Summary
In this chapter, we explored why you will need to upgrade your cluster: either you want to use a new Kubernetes feature or a bug fix or AWS is deprecating the version you are using. We identified you will need to perform three actions for each cluster: upgrade the control plane, upgrade the worker nodes, and upgrade the core components such as kube-proxy
and coreDNS
.
We also discussed how the control plane upgrade is pretty straightforward as it’s a managed service, but node group and component upgrades can be more challenging. Using managed node groups and add-ons simplifies this, but you could also use a second cluster and move the workload between them, upgrading the non-active cluster. This approach—sometimes referred to as blue/green cluster deployments—will add cost and complexity, so it is not recommended, but it can minimize application outages due to upgrades.
In the next chapter, we will look at how you can use AWS Elastic Container Repository...