operator

Bug Report

operator-sdk generate bundle command can only read from pipe but not from STDIN redirected from a file.

Feature Request

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

the kind version is too low, and will not work well on kernel 5.12.2 +
because of kubernetes-sigs/kind#2240

Describe the feature you'd like:

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:

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

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? Azure
• Are you running Postgres Operator in production? yes
• Type of issue? feature request

At t

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.

Describe the bug
Operator doesn't remove sidecar based on annotation, only adds it.

To Reproduce
Steps to reproduce the behavior:

1. Create a deployment with sidecar.jaegertracing.io/inject set to true
2. Spin it up
3. Apply changed deployment with sidecar.jaegertracing.io/inject set to false

Expected behavior
Expect the operator to spin down the agent side car

**Version

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

Happened quite some times with 1.5. There's a KameletBinding called timer-source-to-mysql-sink. It's deleted but then the CLI tries to remove the integration (it should not, it's automatically cleaned up).

[nferraro@localhost kamelet-catalog]$ kamel reset
1 kamelet bindings deleted from namespace camel
could not delete integration timer-source-to-mysql-sink from namespace camel: integr