We currently have quite a few Bash scripts in the scripts/ directory.

I've tried to keep the calling format and structure of these Bash scripts relatively consistent. However, because some of the scripts have roots in other repositories (aws/aws-node-termination-handler, aws/amazon-vpc-cni-k8s, etc), there are inconsistencies in:

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

Describe the bug

When I got a message in slack about any Error the time is wrong

But when we got a message about Update or Create it show the right time

To Reproduce

Expected behavior
in the Error message, it show the correct name.

Screenshots

<img width="593" alt="Screenshot 2020-11-22 at 20 31 18" src="https://user-images.githubusercontent.com/27759761/999138

Currently, we have a simple approach where the operator simply watches the namespace it was created in. But in larger env, multi-namespaces are common. To create mysql cluster in any namespace, we broadly have two approaches (1) Make mysql-operator watch and create mysql clusters in any namespace (2) Continue with current model.
However, current approach is problematic when multiple namespaces ar

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

I cannot find a Helm chart version of it at https://hub.helm.sh
Do you have plans to create one or should everyone do it on their own manually?

Is your feature request related to a problem? Please describe.
The existing example workflows are all quite simple. They don't well represent a real-world workflow.

Describe the solution you'd like
There should be a new workflow example in the examples/ directory which carries out the following steps:

• create namespace
• create deployment
• delete deployment
• delete namespace

Is this a BUG REPORT or FEATURE REQUEST?: Bug Report

What happened: Running go run ./main.go with KUBECONFIG=/Users/scole/.kube/config:/Users/scole/.kube/config-apptio-clusters:/Users/scole/.kube/config-eks causes the startup to fail.

2020-10-29T10:19:12.506+1100	INFO	controller-runtime.metrics	metrics server is starting to listen	{"addr": ":8080"}
2020-10-29T10:19:12.506+1

Is this a BUG REPORT or FEATURE REQUEST?:
FEATURE REQUEST

What happened:
Currently, the output of kubectl get ru is this:

NAME                                   STATUS      TOTALNODES   NODESPROCESSED
rolling-upgrade-nodes-20200616230859   completed   3            3
rolling-upgrade-nodes-20200616234910   completed   3            3

This doesn't tell us what the ASG na