operator

operator-sdk version
operator-sdk version: "v1.13.0-9-g2c1e81a3", commit: "2c1e81a32a36b6ae24156b72f152a3894d4d7b13", kubernetes version: "v1.21", go version: "go1.17.1", GOOS: "linux", GOARCH: "amd64

• Why it's saying me to downgrade my go version?
• What is the workaround?
• I tried with --skip-go-version-check
• But while creating resource following error shows

opera

Feature Request

Is your feature request related to a problem? Please describe:

There are not enough logs in the backend of Chaos Mesh Dashboard.

For example:

https://github.com/chaos-mesh/chaos-mesh/blob/d0dcca20ddf6da79cf4c2bdb682656f0617c24c3/pkg/apiserver/archive/archive.go#L163-L173

When an error occurs, the detail of the error is only introduced in the HTTP response. It

What happened?
I wanted to configure my kubeadm-like cluster to get monitored by prometheus-operator. I started using the following file:

apiVersion: kubeadm.k8s.io/v1alpha1
kind: MasterConfiguration
api:
  advertiseAddress: 192.168.1.173 (I changed the IP from here)
  bindPort: 6443
authorizationModes:
- Node
- RBAC
certificatesDir: /etc/kubernetes/pki
cloudProvider:

What Happened

The home page for Litmus Experiment Docs is not responsive for mobile screens and the dark mode.

What You Expected to Happen

The home page should be responsive and view the content appropriately on the mobile screen. Also, the colors should invert properly upon switching to dark mode.

How to Reproduce It

1. Access [Litmus Experiment Docs](https://litmuschaos.github

Initial questions

• Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.7.0
• Where do you run it - cloud or metal? Kubernetes or OpenShift? Kubernetes on GKE
• Are you running Postgres Operator in production? no - not yet
• Type of issue? feature request

Background

In #1638 I described in detail the process I went thro

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

Feature
Add a new flag to the controller and webhook server to allow you to define the default scaleDownDelaySecondsAfterScaleOut value preventing the need to have this attribute to all your runners if the default of 10 minutes doesn't work for your environment.

Constant set here
https://github.com/actions-runner-controller/actions-runner-controller/blob/master/controllers/horizontalrun

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

I can't find any documentation about upgrading mysql-operator from 0.4 to 0.5.