operator

Feature Request

Describe the problem you need a feature to resolve.

The basic scorecard test fails simply stating error spec does not exist but it does not tell you which CR is affected.

$ operator-sdk scorecard bundle --selector test=basic-check-spec-test --verbose
DEBU[0000] Debug logging is set                         
--------------------------------------------------

Feature Request

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

There are not enough logs in the backend of Chaos Mesh Dashboard.

For example:

https://github.com/chaos-mesh/chaos-mesh/blob/d0dcca20ddf6da79cf4c2bdb682656f0617c24c3/pkg/apiserver/archive/archive.go#L163-L173

When an error occurs, the detail of the error is only introduced in the HTTP response. It

What happened?
I wanted to configure my kubeadm-like cluster to get monitored by prometheus-operator. I started using the following file:

apiVersion: kubeadm.k8s.io/v1alpha1
kind: MasterConfiguration
api:
  advertiseAddress: 192.168.1.173 (I changed the IP from here)
  bindPort: 6443
authorizationModes:
- Node
- RBAC
certificatesDir: /etc/kubernetes/pki
cloudProvider:

What Happened

The home page for Litmus Experiment Docs is not responsive for mobile screens and the dark mode.

What You Expected to Happen

The home page should be responsive and view the content appropriately on the mobile screen. Also, the colors should invert properly upon switching to dark mode.

How to Reproduce It

1. Access [Litmus Experiment Docs](https://litmuschaos.github

Please, answer some short questions which should help us to understand your problem / question better?

• Which image of the operator are you using? e.g. registry.opensource.zalan.do/acid/postgres-operator:v1.6.3
• Where do you run it - cloud or metal? Kubernetes or OpenShift? AWS K8s | Azure
• Are you running Postgres Operator in production? yes
• Type of issue? [Bug report,

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.

Hi,

I'm integrating jaeger with elastic cloud APM (https://www.elastic.co/guide/en/apm/server/current/jaeger.html). Elastic requires to pass a secret as tag in order to authenticate. Currently it is not possible to mount custom secrets as env variables so I'm forced to expose it as a part of manifest.

I've also tried to do some workaround with volume mounts but it didn't work:

apiVer

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

The operator prints periodically this info:

{"level":"info","ts":1623416979.434832,"logger":"camel-k","msg":"could not find any knative type in namespace camel, last error was: services.serving.knative.dev is forbidden: User \"system:serviceaccount:camel:camel-k-operator\" cannot list resource \"services\" in API group \"serving.knative.dev\" in the namespace \"camel\""}

It looks l