operator

In https://github.com/open-policy-agent/gatekeeper/tree/master/charts/gatekeeper

-IMG ?= controller:latest
+IMG ?= $(IMAGE_TAG_BASE):$(VERSION)

I may be misunderstanding but shouldn't it be v$(VERSION)? As-is it will tag it as 0.0.1

Bug Report

NetworkChaos works with device: eth0, not work with device: eth0@if12

I am not sure if it would be a bug or an enhancement.

We could add a validation webhook, or trim the things after @.

What version of Kubernetes are you using?

N/A

What version of Chaos Mesh are you using?

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

Hi There, noticed there is an environment variable to inject "etcd_host" but there are none in the repo for usernames and password. Could create a PR for that to add them to the operator configmap ?
Could enable etcd3 as well since there are no env variables for v3 (supported by Patroni).
Let me know what you guys think.

When autoscaling a RunnerSet you must set kind: RunnerSet as part of the scaleTargetRef: field, this isn't needed when the HRA is backing a RunnerDeployment. It would be nicer to just always have to set the type so it's less confusing. easier to document and consistent between the 2 runner kinds.

apiVersion: actions.summerwind.dev/v1alpha1
kind: RunnerDeployment
metadata:
  name

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

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

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.

Requirement - what kind of business use case are you trying to solve?

Upgrade the otel dependency packages to the latest version.

Current used version of the otel packages is v0.20.0. This version was published Apr 23, 2021. We should upgrade this dependency to the latest version (v1.7.0 when this issue was opened)

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.