clientRatelimit filter works by counting requests per first X-Forwarded-For header value:

https://github.com/zalando/skipper/blob/0c034b77029a9258a447ff070798190c55bc9abc/ratelimit/registry.go#L117-L122

https://github.com/zalando/skipper/blob/0c034b77029a9258a447ff070798190c55bc9abc/net/net.go#L34-L37

therefore if X-Forwarded-For header is present on incoming request its value would

We already have a procedure for how to configure clients to trust the cluster CA https://strimzi.io/docs/0.14.0/#configuring-internal-clients-to-trust-cluster-ca-str but this doesn't completely address the typical user story where they have a KafkaUser for their app and need to create both keystores and truststores for it. So there's no single place in the docs for users to look when setting t

Currently the documentation is in the form of a bunch of markdown files under the docs folder of the repo. It will be great to have a dedicated website for the project to host the documentation and announcement like releases.

What would you like to be added:

version and appVersion from operator.yaml available as magic template
variables.

Why is this needed:

The immediate use-case I'm thinking for

When installing the operator chart we can check if the prometheus operator api is enabled and install a default ServiceMonitor.

Is your feature request related to a problem? Please describe.
We should expose different metrics from BotKube.
Eg. No of resources scanned, no of events sent to communication channels. etc.

Describe the solution you'd like

1. These metrics can be displayed using @botkube metrics
2. Expose these metrics to prometheus so that user can build his dashboards in Grafana based on BotKub

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

Currently in the generated controllers the argument received by lifecycle hooks is payload. This should be changed to the singular form of the CRD kind.

def add(payload), do: :ok

def add(%{} = todo), do: :ok

We currently add the node role label with the following format:

node-role.kubernetes.io/<roleName>=""

in 1.15, --node-labels in the 'kubernetes.io' namespace must begin with an allowed prefix

node.kubernetes.io/role=<role>

We should address this once 1.15 is GA and find a backwards compatible approach for changing this.

Currently, active-monitor repeats the workflow submissions based on the repeatAfterSec spec parameter.

However, it would be more flexible if we also allowed users to specify how often they want the workflow to run using a cron-like expression.

@pzou1974 had the great suggestion to look at this library to help with parsing cron expressions: https://godoc.org/gopkg.in/robfig/cron.v2