tilt-dev
filter chatty k8s events
Describe the Feature You Want
A user asks:
is it possible for us to filter some k8s events from the output in tilt?
we have these events show up in most workloads because we deploy with istio sidecars: Readiness probe failed: Get "http://10.17.15.229:15021/healthz/ready": dial tcp 10.17.15.229:15021: connect: connection refused
I don't think there's a way to do this right now. I've definitely seen output where these probes show up too often
One option is to throttle the events a bit more aggressively. I vaguely remember we had some code that did this already, but may need to tweak the heuristic....
Another option is to filter out the readiness probe events entirely. We already show readiness status in the UI, so I'm not totally convinced we need to show these.
Yet a third option is to add an API to define filters on kubernetes events that you want to ignore.
Additional context
Related issues: https://github.com/tilt-dev/tilt/issues/3033 (defining filters on logs) https://github.com/tilt-dev/tilt/issues/3814 (filters on container output)
we already have some code that automatically excludes istio containers by name...i also wonder if we could determine when a readiness probe event is coming from istio
