What did you do?

• Create a project and generated the bundle

mkdir memcached-operator
cd memcached-operator
operator-sdk init --domain=example.com --repo=github.com/example-inc/memcached-operator
operator-sdk create api --group cache --version v1 --kind Memcached --resource=true --controller=true
make bundle

What did you expect to see?

• The values are checked.
• we h

After #1031, add network delay will also run iptables commands, so we need to test whether they can work together.

Hello

I would like to have pgbouncer-exporter as a sidecar for the connection pooler.
I don't think it's possible right now.

It would be great to have the same options for sidecars as in the cluster.

Is your feature request related to a problem? Please describe.
Vault has backends for AWS like dynamo and s3. However to use them you should provide credentials. AWS support 2 solutions to eliminate this. IAM roles for Service Accounts and Instance profile roles.
Due to some unknown reason vault requires more time to start when using dynamic creds than explicit definition keys in s3 block o

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

Feature Request

Is your feature request related to a problem? Please describe:

The shared informer factory has called the WaitForCacheSync method, and it is no longer need to call it separately for each controller. We can remove Informer ().HasSynced because it will not be used.

Hello,

It would be really helpful to have a detailed description of all supported custom resource (CR) fields by Jaeger Operator solution, I'd like to suggest K8s API reference at https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.19/ as the example

It's common to do in YAML syntax:

steps:
- marshal:
    json: {}

But the marshaller dependency is not recognized automatically and "camel-jackson" needs to be explicitly added (e.g. using -d). The language inspector can do it automatically.

There is no reason stated in the kubernetes event here:

2s          Warning   CRValidationFailure   Jenkins   Base CR validation failed

The logs:

2019-10-22T09:04:47.894Z        WARN    controller-jenkins      base/validate.go:244    Not found volume for 'backup-script' volume mount in container 'backup' {"cr": "infrastructure", "container": "backup"}
2019-10-22T09:04:47.894Z 

Problem

K8s-event posting can fail to post an event (kind: Event) for any reasons, such as API rate limiting, temporary API failures (HTTP 5xx), control plane connectivity issues, SSL handshake failures, etc.

This leads to the events being lost, while they can represent some value. This applies both to the events created from the per-object logger messages (logger.info(...) from the

Add example manifests for different persistence options (EBS volume / SSD mount / RAM disk)