operator
Here are 790 public repositories matching this topic...
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
-
Updated
May 27, 2022 - Go
ETCD support for DCS
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
-
Updated
Apr 3, 2020 - Go
-
Updated
Jul 16, 2021 - Python
-
Updated
Apr 20, 2021 - Swift
-
Updated
May 30, 2022 - Go
-
Updated
May 29, 2022 - Python
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.
-
Updated
Sep 14, 2020 - Python
-
Updated
May 2, 2022 - Go
-
Updated
May 12, 2022 - Go
-
Updated
Mar 6, 2022 - 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.
Tenant Metrics
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.
-
Updated
Mar 11, 2020 - Go
-
Updated
Nov 7, 2019 - Go
We don't have a direct way to fill the platform.Spec.Build.PublishStrategyOptions
. It would be nice to include it in the kamel install
as an option.
We should also transform the kaniko-build-cache
option to fit into the new model.
Originally posted by @squakez in apache/camel-k#1238 (comment)
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."
What is the URL of the document?
Needs to be created
Which section(s) is the issue in?
Needs to be created
What needs fixing?
Helm operators do not allow for cluster aware functions to be run in a Helm Chart template. This is due to the dry-run logic that the Helm operators follow for checking if an upgrade is valid. This should be documented so that users who would like to i