-
Feature
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
-
BU Product Work
-
False
-
-
False
-
0
Feature Overview
Provide the ability to specify an optional time slot on which the kube-apiserver cert renewal may be proceed to avoid causing API instability during critical hours for the customer.
Due to automatic renewal of kube-apiserver cert renewal, Cu is not able to pause this process and this is affecting cluster operations during peak hours. Either they want a way to pause this renewal so they can schedule it during night hours instead of peak hours. This is happening during peak hours and API Server returned 502 to some requests hence they want to schedule these renewals during night times.
https://issues.redhat.com/browse/RFE-3055
https://issues.redhat.com/browse/RFE-1994
Might need coordination with https://issues.redhat.com/browse/RFE-2799
Goals
- Have cluster admin to optionally be able to define time slots where kube-apiserver cert renewal can proceed
- Test the feature
- Document how to use the feature
- blocks
-
RFE-3055 Stop/Pause Automatic Renewal of kube-apiserver cert renewal
- Rejected
- incorporates
-
RFE-3719 Allow cluster-admin to delay kube-apiserver rollout time on SNO
- Rejected
- is related to
-
RFE-3492 [openshift-apiserver] - No pruning/clean of audit and revision-status in openshift-apiserver
- Accepted
-
OCPSTRAT-485 Prune & clean audit and revision-status in openshift-apiserver
- Backlog