You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 28, 2020. It is now read-only.
I have an issue with the operator that I am unable to reproduce consistently but it keeps happening every now and again.
I have a 3-node cluster set up in DigitalOcean hosted kubernetes
apiVersion: apps/v1kind: Deploymentmetadata:
name: etcd-operatornamespace: etcdspec:
replicas: 1selector:
matchLabels:
name: etcd-operatorstrategy:
type: Recreatetemplate:
metadata:
labels:
name: etcd-operatorspec:
containers:
- name: etcd-operatorimage: quay.io/coreos/etcd-operator:v0.9.4command:
- etcd-operator# Uncomment to act for resources in all namespaces. More information in doc/user/clusterwide.md#- -cluster-wideenv:
- name: MY_POD_NAMESPACEvalueFrom:
fieldRef:
fieldPath: metadata.namespace
- name: MY_POD_NAMEvalueFrom:
fieldRef:
fieldPath: metadata.nameresources:
limits:
cpu: 300mmemory: 200Mirequests:
cpu: 50mmemory: 50Mi
At some point a second operator pod appears and the first one loses leader election gets stuck in Terminating state with a final log message like this:
level=fatal msg="leader election lost"
What's really strange to me is that my deployment has 2 out of 1 replicas. Any ideas why this might be happening?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have an issue with the operator that I am unable to reproduce consistently but it keeps happening every now and again.
I have a 3-node cluster set up in DigitalOcean hosted kubernetes
Here is my operator definition:
At some point a second operator pod appears and the first one loses leader election gets stuck in Terminating state with a final log message like this:
What's really strange to me is that my deployment has 2 out of 1 replicas. Any ideas why this might be happening?
The text was updated successfully, but these errors were encountered: