Can anybody tell me whether there is a way to modify or control the retention policy for Rancher logs?
Specifically, the short-lived container logs and any other logs useful for realtime tracking of occasional Rancher glitches?
Is there a way to persist such logs?
12/20/2022, 11:57 PM
We solve this by using Filebeat on all our RKE2 clusters.
Filebeat runs on all cluster as a demonset, then pipes all logs from the nodes to ELK for processing.
This allows us to choose our own log retention.
I'm sure you could do a similar method for your cluster running Rancher.