Is this a BUG REPORT or FEATURE REQUEST?:

/kind feature

What happened:

From time to time, liveness probes do not behave as expected by the person that configured them and some conditions external to the container may make them fail (e.g. dependency on a database) and provoke endless restart loops.
This makes it hard to debug those containers and/or get the system back to normal.

What you expected to happen:

I'd like to be able to disable a liveness probe on a existing pod without replacing it.
Ideally, this would apply to running containers, without waiting them to be restarted.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

This was suggested in the past (without the dynamic part):

At some point we'll probably want to add an enable/disable boolean, since it's convenient to be able to disable liveness probes without losing the parameter settings, but that's less critical than the above.

cf. #12866 (comment)