operator
Here are 742 public repositories matching this topic...
Feature Request
Is your feature request related to a problem? Please describe:
At present, Dashboard supports setting TTL for archived events and experiments, but schedule and workflow do not. We can extend to this [function](https://github.com/chaos-mesh/chaos-mesh/blob/master/pkg/
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
-
Updated
Feb 23, 2022 - Go
- Which image of the operator are you using? The latest, I'm looking at the codebase.
- **Where do you run it - Metal. Kubernetes.
- Type of issue? - Bug report.
Sometimes secrets don't show up for a few moments, for example if using ExternalSecrets.
The [current code](https://github.com/zalando/postgres-operator/blob/master/pkg/cluster/k8sres
-
Updated
Apr 3, 2020 - Go
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
-
Updated
Jul 16, 2021 - Python
-
Updated
Apr 20, 2021 - Swift
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
-
Updated
Sep 14, 2020 - Python
-
Updated
Feb 22, 2022 - Go
-
Updated
Dec 17, 2021 - Go
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.
-
Updated
Feb 23, 2022 - Python
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
-
Updated
Feb 16, 2022 - Go
-
Updated
Apr 27, 2021 - Go
Describe the bug
Cassandra schema job is failed when options.cassandra.servers has multi-server address list (Docker image version is: jaeger-operator:1.22.1)
logs from jaeger-cassandra-schema-job
socket.gaierror: [Errno -2] Name or service not known
Cassandra is still not up at scylla-jaegerdb-dc1-a1-0,scylla-jaegerdb-dc1-a1-1,scylla-jaegerdb-dc1-a1-2:9042. Waiting 1 second.
-
Updated
Mar 11, 2020 - Go
-
Updated
Nov 7, 2019 - Go
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.
Tenant Metrics
Improve this page
Add a description, image, and links to the operator topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the operator topic, visit your repo's landing page and select "manage topics."
Type of question
General operator-related help
Question
What did you do?
I update the same CR twice in the short time, and different workers get key from work queue, will it happen that two workers reconcile different events on the same CR ? How to ensure that the new event reconcile finished finally instead of the old one reconcile finished finally?
Puzzled: if watch tw