The Wayback Machine - https://web.archive.org/web/20210811023815/https://github.com/topics/operator
Skip to content
#

operator

Here are 630 public repositories matching this topic...

chaos-mesh
DiazRock
DiazRock commented Jun 8, 2021

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:
litmus
apeschel
apeschel commented Jul 6, 2021

Please, answer some short questions which should help us to understand your problem / question better?

  • Which image of the operator are you using? e.g. registry.opensource.zalan.do/acid/postgres-operator:v1.6.3
  • Where do you run it - cloud or metal? Kubernetes or OpenShift? AWS K8s | Azure
  • Are you running Postgres Operator in production? yes
  • Type of issue? [Bug report,
alekskar
alekskar commented Jun 18, 2020

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

kopf
nolar
nolar commented Aug 20, 2020

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

nicolaferraro
nicolaferraro commented Jul 8, 2021

Happened quite some times with 1.5. There's a KameletBinding called timer-source-to-mysql-sink. It's deleted but then the CLI tries to remove the integration (it should not, it's automatically cleaned up).

[nferraro@localhost kamelet-catalog]$ kamel reset
1 kamelet bindings deleted from namespace camel
could not delete integration timer-source-to-mysql-sink from namespace camel: integr

Improve this page

Add a description, image, and links to the operator topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the operator topic, visit your repo's landing page and select "manage topics."

Learn more