PDB not looking for main container

[snaslai]

We have a PDB defined on a pod with four containers, when the pod is going through rolling upgrades, the old pod is terminated before the new pod has all the four containers up and running because the pod is in running state if three out of the four containers are running, which does not serve the purpose because our main container is still not up, which affects the user application availability

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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-sigs/prow repository.

[dipesh-rawat]

This seems more like a support question or usage inquiry rather than an issue with the current state of the Kubernetes documentation.

/kind support
(Feel free to remove the label if this is incorrect.)

[shurup]

I agree; it looks more like a support request, which is not directly related to the documentation itself. Our community page lists various places where you can reach enthusiasts who might help solve your issue. More specifically, I would recommend Slack and Server Fault to discuss your case.

[lmktfy]

/close not-planned

[k8s-ci-robot]

@lmktfy: Closing this issue, marking it as "Not Planned".

In response to this:

/close not-planned

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-sigs/prow repository.