changing 1h to 1d to make it easier to view today's events

[da0x]

Viewing today's events is useful, and not sure if 30m vs 1h makes too much sense. If others vote this up then maybe it's worth changing.

[jboyens]

Having the opposite of this would be useful for me. Sometimes we have 10K events in the last hour and k9s becomes completely unusable at that level of events (i.e. must be killed).

[nublarsec]

Kubernetes Event objects are stored in Etcd and it only keeps the last hour's worth of Events, to keep from burdening Etcd storage. Adding higher time ranges won't show more historical events, unfortunately.

@derailed you may want to close this as I don't believe it's possible.

@da0x Other alternatives are to ship those Events somewhere else where they can be stored/indexed/viewed. Here are a few tools that turn K8s Event objects into JSON log messages, so you can ingest them into something like Elasticsearch or Loki.

• eventrouter - formerly Heptio, then VMware, now archived
• openshift/eventrouter - fork from eventrouter with current activity
• Grafana Agent