kubernetes-controller

Is your feature request related to a problem?
Each of the repositories contains their own pull request templates. These could be standardised to maintain consistency throughout each of the products.

Describe the solution you'd like
Default community health files, stored in a separate .github repository (aws-controllers-k8s/.github) is offered to standardise across entire Github or

Describe the solution you'd like
BotKube doesn't support multi-arch images as of now. With goreleaser it will ease the process of building multi-arch binaries/docker images and publishing it.

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, 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

This would allow in the use case where you may have more than 1 DNS server to query (for redundancy)

edgeDNSServer: &edgeDNSServer:
  - 1.1.1.1
  - 2.2.2.2 

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?

Some basic default readiness/lieness Probes would be may a good idea too (e.g. tcp socket check), better then nothing?

Originally posted by @spielkind in mittwald/kube-httpcache#51 (comment)

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

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 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