3 years ago

Category: Kubernetes, Docker

If you’re running Kubernetes on GKE, chances are there’s already some form of upgrades for the Kubernetes clusters in place. The focus of this blog is how one can attempt to keep up with this release cycle.

The process of master node upgradation is very opaque in nature, as GKE manages the upgrade for you and not the cluster operator, which might not give you a lot of visibility on what exactly is happening.

Kubelet is the process, which actually listens to the api-server for incoming instructions to schedule/delete pods to the node in which it is running.

For stateless applications, the simplest thing to do is to increase the replicas to reflect the number of zones in which your nodes are present.