adriananeci

I can give it a try if there are no other concerns regarding this approach.

Hey @joshulyne , `Reporting took too long to complete and timed out` is an internal reporting message related to the check itself and not to kuberhealthy. Maybe the message is...

Hey @joshulyne Thanks for your reply. Check run interval and timeout is configured as: ``` runInterval: 1m timeout: 1m ``` Looking deeper into the logs I can see that for...

Deployed it on a test cluster and it seems to have fixed the race condition. No `Failed to write new UUID for check because object was modified` in logs and...

Velero logs might contain sensitive information as I noticed, so not sure if I'll be able to provide a full bundle since we're noticing this problem only on big clusters,...

/remove-lifecycle-stale

@Glitchm While your approach suppress the error, it is not catching the real issues. For example, given the following CRD spec: ``` apiVersion: apiextensions.k8s.io/v1 kind: CustomResourceDefinition metadata: name: test.crd.com spec:...

We've started getting OOMs on big clusters, and we're looking to dynamically adjust resource limits and avoid manually scaling VPA components every time we hit a new threshold.

@damemi Thanks for your thoughts. Please be aware that in case of `Taint based Evictions`: ``` Note: Kubernetes automatically adds a toleration for node.kubernetes.io/not-ready and node.kubernetes.io/unreachable with tolerationSeconds=300, unless you,...

I'm able to successfully login to the private registry using `docker login` locally, but still no luck with validating images. I'm still getting `Unable to get image data` 1. Validate...