3 years ago

Category: Software, Database, Data, Kubernetes, containerization

Changes are part of all software life cycles but how do we make sure changes are made safely in Kubernetes (k8s)? We will tackle changes to the application, pods, and the underlying infrastructure by leverage k8s’ RollingUpdate property and Pod Disruption Budgets respectively.

Deployments provide a feature for defining how to perform rolling updates on pods.

Since replica is 10, at most you will see 14 pods and at least you will see 6 pods.

When a readiness probe is failing, k8s will not send traffic to the pod and will mark the pod as Unready.