You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Environmental Info:
K3s Version: 1.27
(originally 1.23 or 1.24)
Cluster Configuration:
3 masters(servers) + workers(agents),
(originally 1 master with sqlite as DB)
Describe the bug:
I have this cluster for a year and i noticed i still have events from 200+ days ago
i tried to google but i only get info about the containers/images garbage collection..
so i have several questions
aren't events supposed to be garbage collected periodically by default?
does k3s changes this behavior or makes some custom configuration from upstream kubernetes?
choosing to garbage collect event older than is even an option i can change?
The text was updated successfully, but these errors were encountered:
Environmental Info:
K3s Version: 1.27
(originally 1.23 or 1.24)
Cluster Configuration:
3 masters(servers) + workers(agents),
(originally 1 master with sqlite as DB)
Describe the bug:
I have this cluster for a year and i noticed i still have events from 200+ days ago
i tried to google but i only get info about the containers/images garbage collection..
so i have several questions
The text was updated successfully, but these errors were encountered: