Unexpected startupProbe behavior.

[heckad]

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!

[heckad]

/sig cluster-lifecycle

[heckad]

@neolit123?

[neolit123]

/remove-sig cluster-lifecycle
/sig apps

try asking in #kubernetes-users on k8s slack.

[heckad]

@neolit123, they are silent in the chat. Who is involved in the development of startup probe?

[neolit123]

i think this topic better fits SIG Node.

try asking in their channel on slack #sig-node, but be patient ;)
/sig node
/remove-sig apps

[k8s-ci-robot]

@neolit123: Those labels are not set on the issue: sig/apps

In response to this:

i think this topic better fits SIG Node.

try asking in their channel on slack #sig-node, but be patient ;)
/sig node
/remove-sig apps

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.