Philip Gough
Philip Gough
> whereas it seems that GKE, for example, keeps the Status: Failed Pods around so they can be inspected later on Reading https://github.com/kubernetes/kubernetes/issues/99986 your assumption seems correct. GC is [configurable](https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection)...
We can rebase on https://github.com/observatorium/observatorium/pull/495 when it merges which fixes the docs issue. Assuming ci isn't bricked :/
@bwplotka have you had any success with generating relatively idiomatic clients from OpenAPI spec? If so, what tools did you use?
@saswatamcode - this may be of interest to you since you have done something similar in https://github.com/observatorium/obsctl/ recently I think :)
Relates to stuck dependabot https://github.com/prometheus-operator/kube-prometheus/pull/1766
I created a v1.25.0 with `kind` against current `main` and failed to produce these issues:
Could there be a potentially existing botched install of the stack already on the cluster? It seems like an admission/mutating webhook for the monitoring resources already existed when you tried...
@brancz just weighing in on this with what I have observed running `v0.12.0` as it may be helpful. Heres the relevant config: ```yaml containers: - resources: limits: cpu: '8' memory:...
That makes sense, and answers the question, thanks for providing the details. There was nothing that looked particularly off to me either but since I had the data from the...