1

Scenario:

  • I got 3 replicas of a service running
  • I want to update its version

This is whats happening:

  • The new container will be created
  • As soon the container are switching their status from ContainerCreation to Running kubernetes will start terminating old versions of this container.

Problem: Status Running does not make sure the application is available. How can I prevent kubernetes from terminating services before it is not sure the containers application is available? Maybe adding a necessary health check?

elp
  • 167
  • 1
  • 9

1 Answers1

0

Kubernetes runs readinessProbes to check if a container is actually up for accepting connections. This will be considered when performing a rolling update. While the official Kubernetes documentation on this topic is rather lengthy the blog post Enable Rolling updates in Kubernetes with Zero downtime is a nice summary. Maybe directly check the final deployment file at the end to get the idea.

webwurst
  • 362
  • 2
  • 6