rolling update

Replacing instances of an application with the new version a few at a time while the rest keep serving.

In more detail

It is the default strategy of a Kubernetes Deployment. maxSurge and maxUnavailable bound the extra and missing capacity, and readiness decides when the next replacement may begin. Old and new versions share traffic during the rollout.

Examples

both versions serve traffic at once, so the schema must accept both
strategy:
  type: RollingUpdate
  rollingUpdate:
    maxUnavailable: 0
    maxSurge: 1

Related terms

Taught in

References

Certification courses