-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
event-ttl-kaso
-
None
-
-
100% To Do, 0% In Progress, 0% Done
-
False
-
-
False
-
None
-
None
-
None
We want to customize the --event-ttl duration setting through KAS-O and OpenShift APIs. Currently the default in OpenShift is set to 3h via the defaultconfig.yaml in KAS-O.
There's no validation on Kubernetes side, setting it to 0 will not set a TTL via a lease in etcd - meaning the event will stay forever/until deleted manually.
We should settle on a meaningful minimum in this case, 5m / 10m / 15m?
Currently able to set via KubeAPIServer CRD as a config override:
unsupportedConfigOverrides: apiServerArguments: event-ttl: - 1h
[UPSTREAM]
https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/