operator

What i

The library controller-runtime requires setting a logger (by log.SetLogger()) at the first 30s when the application starts, or it would use the default NullLogSink. We should also call it in testing codes.

When we test with ginkgo, ginkgo provides a helpful GinkgoWriter, which hides the output as default, only prints it when the test failed. We'd better use it to keep our testing output

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

Currently it is only possible to specify cpu and memory limits. Given Kubernetes has Huge Page Support, and huge pages are very applicable to databases, I suggest that it would be useful to be able to do the following:

    resources:
      limits:
        cpu: 1
        memory: 1024Mi
        hugepages-2

It is set to "array" when it should be set to "object". This makes it unusable and creates validation errors when specifying dnsConfig in normal PodSpec format using a map as normal. Please correct.

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.

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

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.

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.