Jonathan Phan

This could be coming from the kube-apiserver -- I'm noticing a lot of logs similar to these on an apiserver pod when this happens: ``` W0825 21:07:43.336449 1 watcher.go:342] Fast...

An external checker for a deployment and service has been created for 2.0.0. #226

This has been done for deployment & daemonset

No, this still utilizes Lambdas

Should this be querying and checking the metadata service instead? `"http://169.254.169.254"`

Looks like this might be an issue related to how we generated our CRDs -- leaving this here as a note for later reference: ``` https://github.com/kubernetes/kubernetes/issues/58311 https://github.com/kubernetes/kubernetes/issues/66899 https://github.com/kubernetes/kubernetes/issues/86811 https://github.com/kubernetes/code-generator/tree/master/examples/crd/apis/example/v1 https://github.com/kubernetes-sigs/cluster-api/blob/bf790fc2a53614ff5d3405c83c0de0dd3303bb1f/api/v1alpha2/common_types.go#L46-L67...

Yes! You would have to manually wipe the CRDs unfortunately. The CRD changes I made from `v2.6.0` -> `v2.7.0` updates kuberhealthy CRDs to different k8s objects. Instead of `apiextensions.k8s.io/v1beta1` the...

Leaving this one open for awareness.