Enable users to control whether a pod should be marked as unready during in-place updating some containers.
Why is this needed:
In Kruise, we have introduced the InPlaceUpdateReady readiness gate, which is set to not ready before initiating an in-place update for a container.
When utilizing Kruise to perform in-place updates on less critical containers, there is a limitation: even if you configure the CloneSet lifecycle, you cannot prevent the pod from being marked as not ready during the update process.
What would you like to be added:
Enable users to control whether a pod should be marked as unready during in-place updating some containers.
Why is this needed:
In Kruise, we have introduced the InPlaceUpdateReady readiness gate, which is set to not ready before initiating an in-place update for a container.
When utilizing Kruise to perform in-place updates on less critical containers, there is a limitation: even if you configure the CloneSet lifecycle, you cannot prevent the pod from being marked as not ready during the update process.