kubernetes-controller

I'm using the apigatewayv2 controller and I'm trying to control where my application is being created. I have a specific nodes for controllers but since I don't have an affinity attribute I need to save the chart locally and add the affinity attribute by myself. It's a bit frustrating since I don't want to manage this chart.

Describe the solution you'd like
Saved the chart locally and add

I have a secure Webhook endpoint to which i like to have botkube send the events. How should i add the Authorization header for Webhook?

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

I can't find any documentation about upgrading mysql-operator from 0.4 to 0.5.

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?

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