kubernetes-controller

As of currently, Helm is the recommended way of installing ACK service controller(s). ACK Helm charts support the fields for IRSA in values.yaml , which makes it possible to execute single helm install command and get ACK service controller up and running with IRSA.

This is a very good experience however this does not extend to authorization mechanism other than IRSA.

If ACK customers

Describe the bug

To Reproduce
Steps to reproduce the behavior:

1. I tried to install botkube helm chart and integrate it with Elasticseach which is installed in one of VM'
2. POD get to install successfully but in logs, I can see below error
   ERRO[2021-09-21T10:04:06Z] Failed to get index. Error: Head "https://xxxyz:9201/esskube-2021-09-21": x509: certificate signed by unknown author

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

For now, under "podSpec" - there is no way to set resources limits and requests for pt-heartbeat container from mysqlcluster's statefulset.

Please add option for pt-heartbeat like mysqlOperatorSidecarResources and metricsExporterResources.

Most of the current use cases, automated tests and functional test scenarios were performed in context of 2 clusters only as it is most common and easier to test setup.

Meanwhile we need to be ready and test for >2 scenario cluster scenario.

This series of testing can reveal potential edge cases in current LB strategies implementation and can lead to LB logic extension and handling of >2 num

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?

We should write some documentation for the GameServer API.

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)

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

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