Tolerate unready ceph-mon endpoints
This allows ceph to form a reliable quorum under Kubernetes 1.6. There appears to be a minor timing difference in 1.6 compared to previous versions requiring us to annotate the ceph-mon service with this toleration. Change-Id: I2bb325c6dc0fc4b3c98eaccd95be36a53b1e8a16
This commit is contained in:
parent
60d01e54cc
commit
6dc0852146
@ -20,6 +20,14 @@ metadata:
|
|||||||
labels:
|
labels:
|
||||||
app: ceph
|
app: ceph
|
||||||
daemon: mon
|
daemon: mon
|
||||||
|
annotations:
|
||||||
|
# In kubernetes 1.6 and beyond, it seems there was a change in behavior
|
||||||
|
# requiring us to tolerate unready endpoints to form a quorum. I can only
|
||||||
|
# guess at some small timing change causing statefulset+2 to not see the
|
||||||
|
# now ready statefulset+1, and because we do not tolerate unready endpoints
|
||||||
|
# a newly provisioned ceph-mon will most certainly never see itself in the
|
||||||
|
# peer list. This change allows us to form a quorum reliably everytime
|
||||||
|
service.alpha.kubernetes.io/tolerate-unready-endpoints: "true"
|
||||||
spec:
|
spec:
|
||||||
ports:
|
ports:
|
||||||
- port: {{ .Values.network.port.mon }}
|
- port: {{ .Values.network.port.mon }}
|
||||||
|
Loading…
x
Reference in New Issue
Block a user