operator

Feature Request

Describe the problem you need a feature to resolve.

When creating a bundle (make bundle), you are prompted for a few fields, including Comma-separated list of maintainers and their emails (e.g. 'name1:email1, name2:email2') (required): - this makes it look like you need to add single quotes, e.g. 'Brendan Bergen:foo@example.com', though, if you add these quotes,

Bug Report

What version of Kubernetes are you using?

1.20.0
What version of Chaos Mesh are you using?

v2.1.1
What did you do?

README.md is still pointing to addons/strip-limits.libsonnet addon as a way to strip containers from set resource limits. However since release-0.8 resource requests are first-level settings and users should use

We can add an upgrade/downgrade command for litmusctl binary, it can look at the matrix of versions in a file and upgrade/downgrade according to the user's choice.

example

• litmusctl upgrade v0.5.0
• litmusctl downgrade v0.4.0

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

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

Hi
Th

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

I wanted to use topology spread constraints to control how Pods are spread across in my cluster by topologySpreadConstraints section in runner deployment. But i faced to following error: `error validating data: ValidationError(RunnerDeployment.spec.template.spec): unknown field "topologySpreadConstraints" in dev.summerwind.actions.v1alpha1.RunnerDeployment.spec.template.spec; if you choose to ig

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.

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

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

For now, under "podSpec" - there is no way to set resources limits and requests for pt-heartbeat container from mysqlcluster's statefulset.

Please add option for pt-heartbeat like mysqlOperatorSidecarResources and metricsExporterResources.