We have a deploy with Consul and other application pods.

All Consul client pods are running and inside pod status test I ran is OK.

The application pod that is running readiness-check is stuck in status waiting for the Consul to get ready - which it is.

I took a look in the master code and saw that since version 2.0.0 the ready check was changed and now it is checking for container kind, but the Consul (and also Fluentbit, Prometheus etc.) will not get tested as they are DaemonSet kind.

Also, there is an error in the function read_name that is causing the error:

ERROR - Exception when calling list_namespaced_pod: 'V1ObjectMeta' object has no attribute 'owner_reference'