What is the URL of the document?

i.e.: https://sdk.operatorframework.io/docs/building-operators/golang/installation/

Which section(s) is the issue in?

Prerequisites

What needs fixing?

Consider add $ operator-sdk version.

Additional context

We could not reproduce the documentation because the commands may incomplete to the current version of operator-sdk.

Bug Report

https://github.com/chaos-mesh/chaos-mesh/blob/master/controllers/awschaos/ec2stop/types.go#L56-L60 These lines of codes make it possible to use another endpoint (like localstack) to do AWS experiments. However, the Recover of ec2stop and other kinds of chaos doesn't have these codes.

It was amazing that even with this bug, the integration test has passed. The expected pheno

What is missing?
kube-prometheus ships by default grafana, but there are no alerts around it. Since upstream project has a monitoring mixin we may as well use it.

Why do we need it?
To provide alerts/dashboards for grafana OOTB.

• Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.6.2
• Where do you run it - cloud or metal? Kubernetes or OpenShift? Bare Metal K8s (kubeadm)
• Are you running Postgres Operator in production? yes
• Type of issue? [Bug report, question, feature request, etc.] Documentation/actual behavior mismatch

For additionalVolumes

Currently, we have a lot of env vars in the litmusportal, so we need to use envconfig pkg to validate and process the env vars.
PKG- https://github.com/kelseyhightower/envconfig

Need to add in:

• graphql-server
• event-tracker
• subscriber
• authentication-server

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.

The label isn't helping as I thought it would. In fact, it's only causing noise. This issue is about removing the issue labeler workflow:

https://github.com/jaegertracing/jaeger-operator/blob/master/.github/workflows/labeler.yml

And its configuration file:

https://github.com/jaegertracing/jaeger-operator/blob/master/.github/labeler-needs-triage.yaml

Running operator against OpenShift 4.6 and noticed:

W0322 15:58:35.370055   10528 warnings.go:67] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress

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