From b9f0b04e58bc34c62ebb295eae0f8d9eb0aceed7 Mon Sep 17 00:00:00 2001 From: Alex Robinson Date: Thu, 29 Sep 2016 15:36:55 -0400 Subject: [PATCH] Don't tolerate unready endpoints in cockroachdb example That was only included in the initial config due to cargo-culting, and has the potential to break node startup if it resolves its own address to gossip to. --- examples/cockroachdb/cockroachdb-petset.yaml | 2 -- 1 file changed, 2 deletions(-) diff --git a/examples/cockroachdb/cockroachdb-petset.yaml b/examples/cockroachdb/cockroachdb-petset.yaml index 87349925370..ca172bce0a8 100644 --- a/examples/cockroachdb/cockroachdb-petset.yaml +++ b/examples/cockroachdb/cockroachdb-petset.yaml @@ -24,8 +24,6 @@ apiVersion: v1 kind: Service metadata: annotations: - # Make sure DNS is resolvable during initialization. - service.alpha.kubernetes.io/tolerate-unready-endpoints: "true" # Enable automatic monitoring of all instances when Prometheus is running in the cluster. prometheus.io/scrape: "true" prometheus.io/path: "_status/vars"