Feature Request

Describe the problem you need a feature to resolve.

I want to know when new operator-sdk binary and plugin versions are available when running certain operator-sdk commands

Describe the solution you'd like.

When I run an operator-sdk command, I want t

There is no e2e test and documents for external network delay and partition now 🤦 .

The e2e test could be found in /test/e2e/chaos/basic.go. Reading other tests in that file could help accomplish this issue.

Example for extern network delay:

apiVersion: chaos-mesh.org/v1alpha1
kind: NetworkChaos
metadata:
  name: network-netem-example
  namespace: chaos-testing
spec:

What is missing?
Not all objects created with kube-prometehus have recommended set of labels

Why do we need it?
To comply with best practices and allow easier dependency discovery

Environment

• kube-prom

• Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.5.0
• Where do you run it - cloud or metal? Kubernetes or OpenShift? GKE
• Are you running Postgres Operator in production? no
• Type of issue? Bug/Feature

The Postgres Operator currently supports setting [custom TLS certificates](https://postgres-operator.readthedocs.io/en/lat

This issue is to dockerize the litmus demo repository to run a demo experiment with the minimal prerequisites. Currently, there are certain numbers of prerequisites to run the litmus demo env, this can be reduced by containerizing the dependencies and running the script from it.

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.

According to the istio annotation docs, the sidecar.istio.io/inject annotation should only be applied to pods - see: https://istio.io/latest/docs/reference/config/annotations/.

$ istioctl analyze -A
Warn [IST0107] (Deployment jaeger-collector.observability) Misplaced annotation: sidecar.istio.io/inject can only be applied to Pod
Warn [IST0107] (Deployment jaeger-query.observability

File: examples/routes.groovy

Logs:

[1] 2020-12-03 16:41:56,092 WARN  [org.apa.cam.com.tim.TimerConsumer] (Camel (camel-1) thread #0 - timer://groovy) Error processing exchange. Exchange[19B282B64B1E822-0000000000000003]. Caused by: [groovy.lang.MissingPropertyException - No such property: DELEGATE_FIRST for class: org.apache.camel.k.loader.groovy.dsl.BeansConfiguration]: groovy.lang.Mis

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

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