If you attempt to create a Bucket with the same name as a Bucket that you recently deleted, you might run into this:

OperationAborted: A conflicting conditional operation is currently in progress against this resource.

This is due to S3 queuing the delete operation and the need to have a unique name of the bucket for the account. Attempting to create the Bucket with the same name v

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

In e2e test suite, we mock resource creation with fake client and verify the BotKube event generations.
https://github.com/infracloudio/botkube/blob/develop/test/e2e/notifier/create/create.go#L46

We need to add similar test cases to verify delete event handling.
We can use Delete API for Deleting a resource.

Add te

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

Some log entries are using V(1) but still get emitted by default.
We should have a way to mute debug logs using a flag.

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