How to lengthen retention of events of current Cluster?

Rancher 2.x
1

In the Rancher Dashboard there is a “Events of current Cluster” section

I saw that they disappear after a few hours

Is it possible to lengthen the conservation of these events?

2

This is a Kubernetes configuration and the setting and the design considerations are in https://github.com/kubernetes/kubernetes/issues/52521

3

Thank you
I understand that i must configure the ttl of events as i wish by
setting the flag --event-ttl duration Amount of time to retain events. (default 1h0m0s) of kube-apiserver

how do I set that flag on Rancher?

4

This is described on https://rancher.com/docs/rancher/v2.x/en/faq/technical/#how-can-i-add-additional-arguments-binds-environment-variables-to-kubernetes-components-in-a-rancher-launched-kubernetes-cluster

5

I don’t understand the guide
I searched for the event-ttl property in the full cluster yml example, without finding it

The guide says to add properties in the extra_args section

So I modified the cluster yaml, adding the property like this:

services:
etcd:
extra_args:
event-ttl: 72h

Now the cluster is in error:

[etcd] Failed to bring up Etcd Plane: etcd cluster is unhealthy

Also, I should set this flag in kube-apiserver, but the guide only talks about extra-args

6

in the “full cluster yml example” there is extra_args under kube-api
services:
–etcd:
–kube-api:
----extra_args:
------event-ttl: “72h0m0s”

Note: the hyphens are just for indentation

7

Works perfectly for rke1, but i cannot get it to work for rke2. It just disappears from the cluster yaml after saving:

spec:
defaultPodSecurityPolicyTemplateName: “”
kubernetesVersion: v1.23.6+rke2r2
localClusterAuthEndpoint: {}
rkeConfig:
chartValues:
rke2-calico: {}
kubeApi:
extraArgs:
event-ttl: 96h0m0s
etcd:
…