-
Feature Request
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
-
None
-
None
-
None
What are you experiencing? What are you expecting to happen?
Currently the TTL for events is 3 hours, I can see KCS document which states we cant change the duration
https://access.redhat.com/solutions/6968044
Define the value or impact to you or the business
- Namespace are creating too much events, resulting in high etcd db size, client would like to have this configured to have 3 hours or less, usually 1 hour as in a regular kubernetes intallation
- causes
-
OCPSTRAT-2095 Add support for event-ttl in Kube API Server Operator
-
- Release Pending
-
- is duplicated by
-
RFE-7051 Separate ETCD instance for Kubernetes events in OpenShift
-
- Refinement
-
- links to