The E2E tests sometimes fail during setup with the message:

 ERROR: 1 setup jobs failed. Check logs above for details. 

-- https://prow.build-infra.jetstack.net/view/gcs/jetstack-logs/pr-logs/pull/jetstack_cert-manager/3647/pull-cert-manager-e2e-v1-20/1359494849920765955#1:build-log.txt%3A668 (thanks @irbekrm )

The setup jobs are launched as background shell jobs:

• https://gi

pods, err := selector.SelectAndFilterPods(ctx, r.Client, r.Reader, &dnschaos.Spec, config.ControllerCfg.ClusterScoped, config.ControllerCfg.TargetNamespace, config.ControllerCfg.AllowedNamespaces, config.ControllerCfg.IgnoredNamespaces)

This line of code occurs several times in Chaos Mesh code base, and most of these config.xxx.xxx won't change during the runtime. Please construct

Currently, the litmus portal’s backend logs aren’t meaningful and formatted. Also, It’s difficult to find the root cause of any litmus portal component failure by going through the logs.

The requirements of this issue are:

• Use a common go pkg like logrus/glog/klog across all litmus portal’s backend components
• Add meaningful log on the edge cases
• Format the existing log.

List of c

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