Eric Greer

I am not against it... We could probably fetch the labels off the `podSpec` and `extraLabels` fields from the `khcheck` or `khjob` that created the pod.

Yeah, that was a big helm chart bump. We recently deployed a new github action that automatically publishes a new revision of the helm chart whenever the specs for it...

Because each new version is essentially one change (the automation fires on every merge to master), we would always have a very small changelog. We also aren't making tags when...

This is an understandable feature request... This would go somewhere in [here](https://github.com/kuberhealthy/kuberhealthy/blob/06c6b9e45ac4186717d825f5e5e6415d1bfb04ff/cmd/kuberhealthy/kuberhealthy.go#L1548)...

I think custom labels for metrics is probably best done as it's own pull request. This sounds like a good feature. It could be added to the khcheck resource. As...

It sounds like the core ask here is that you would like Kuberhealthy to support clusters that do not have a working `cluster.local` DNS zone. Is that a good summary...

It may be that because we can't cause the daemonset spec to skip nodes that are `Not Ready` or otherwise cordoned, that we need a new check that directly creates...

Renamed this issue to describe the path forward. The nature of daemonsets does not enable us to easily skip cordoned nodes, so we need to make a check that pins...

We need to better define what options this check will have. What will this check allow users to specify? - Tolerations - Node label selector? - pin to single node?...

Sounds like we need a quick verification (until we can get a test) to ensure that the pod restarts check works. @jonnydawg should be able to help.