What problem are you trying to solve?

Some environments have security restrictions which require liveness and readiness probes in order to deploy any container in the cluster. Currently our debug container does not contain these, and there is no easy way for users to add the values into the container due to the way it's injected into the pod but not propagated to the deployment.

How should the problem be solved?

Per discussion, we've agreed to statically code the liveness and readiness probes so the container always passes the checks.

Any alternatives you've considered?

Scraping the debug container entirely in favor of ephemeral containers, but that's a bit out of scope for the issue/ask.

How would users interact with this feature?

they would not. it will be part of the debug container template.

Would you like to work on this feature?

yes