operator

Bug Report

What did you do?

Tried to run a Makefile build by operator-idk, known

Feature Request

This issue will not introduce any NEW features or any changes to the current architecture. It's only about improving the style of codes, and let it be easier to understand Chaos Mesh's codes.

As Effective Go/Interface checks introduced, we do not need to declare explicitly that one struct implements an interface. So

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:

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.

kuttl v0.11.0 has just been released, and we should update our tests to use it.

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

Cobra function cmd.SetOut() does not redirect output for some commands.

for command output redirection this function is used https://github.com/apache/camel-k/blob/d9230bd1f92d2839adb37f819132a2ecd6b92ee4/e2e/support/test_support.go#L1331

redirection works fine for kamel get kamel kit but the output of commands kamel describe kamel help kamel dump kamel version is not being r