I propose to change the behavior of startup probe

Asking for help? Comment out what you need so we can get more information to help you!

Cluster information:

Kubernetes version: 1.18
Installation method: microk8s
Host OS: ubuntu 19.04

If I have startupProbe probe and readinessProbe then all good. Previous version of the pod is terminated after startup probe success, but if readinessProbe wasn’t specified the pod becomes ready immediately. It would be nice to add new state (for example starting) which would have pods until a startupProbe is successful. Also, it would mean that container not ready for connection.

Thank you for attention!

You can format your yaml by highlighting it and pressing Ctrl-Shift-C, it will make your output easier to read.

It’s rare that I say this in this direction, but this is not a support
request, it’s a feature request. Can you please file it on GitHub?

1 Like

I made this 13 days ago https://github.com/kubernetes/kubernetes/issues/89995.

1 Like