Is your feature request related to a problem? Please describe.
@munnerz helped debug this today.

Someone set kubernetes.io/ingress.allow-http: "false" on an Ingress resource. When time came to refresh the cert it just hung forever with no errors or event or anything.

Describe the solution you'd like
I'd have liked to see an Event and/or Condition on the Ingress saying "cert-mana

chaos-daemon doesn't have any authentication mechanism, which means any client in the cluster could modify the iptables and ipset config / cause stress / inject IO latency for nearly all the pods.

gRPC with server side SSL/TLS authentication is enough. However, it may break the chaosctl (which is definitely an evidence for the risk), or we need to distribute the certificate to it (or it can

This issue is

Feature Request

Is your feature request related to a problem? Please describe.
The adoption and operator controllers have not updated their method signatures to use the client.Object instead of the runtime.Object.

Describe the solution you'd like
The methods in the controllers mentioned above should be updated to use the client.Object interface.

What would you like to be added:
Currently, kubectl kudo version only prints the current version of the KUDO CLI. It should also print the version of the KUDO controller if the con

Currently the env variables injected are specific to this docker image https://github.com/barney-s/docker-airflow

Align it with https://github.com/puckel/docker-airflow and make necessary changes in the operator to make it work with both.

related to GoogleCloudPlatform/airflow-operator#10