Thomas Jungblut
Thomas Jungblut
/lgtm /label backport-risk-assessed
/remove-lifecycle rotten
/label backport-risk-assessed
Turns out we have a case where we ran out of the size aspect of the objects. We get the logs from apiserver: ``` I0821 23:03:24.662977 17 trace.go:205] Trace[419549052]: "List(recursive=true)...
As a start, I've quickly added a metric that allows us to alert on common large range requests (secrets / configmaps / image streams) with #16881.
We're also seeing those bursty workloads more and more often, eg with argo and batch-style operations. > So, I am seeking a way to compact old revisions in time. It's...
I'm also +1 for removing it. WDYT about adding a timestamp to endpoint/status? That way we can still have some indication when we go through (disconnected) customer logs.