+++ This bug was initially created as a clone of Bug #1774121 +++ > Details of feature and work involved is captured here: https://jira.coreos.com/browse/PROD-970 We should be backporting this capability to 4.1.z to keep customers on this version from seeing an issue with Service CA's
All pods on the cluster are updated every time a user does an update. So they are taking that downtime to update no matter what - we could potentially align the fix with a rolling update (on a z).
(In reply to Clayton Coleman from comment #4) > All pods on the cluster are updated every time a user does an update. So > they are taking that downtime to update no matter what - we could > potentially align the fix with a rolling update (on a z). Is this a suggestion to do: https://github.com/openshift/enhancements/pull/193
Can this bug be closed given that we don't intend to automate rotation for 4.1?
This might get closed WONTFIX, but if not, any backports should include the fix from the bug 1810036 series.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days