From 6574cd58aa14e90a9ee32fe6ea83c742040c35ca Mon Sep 17 00:00:00 2001
From: Joshua Olson <joshua.olson.490@gmail.com>
Date: Mon, 6 Aug 2018 12:48:19 -0500
Subject: [PATCH] kube-prometheus: change the 3 etcd client cert files back to
 files that actually exist in this repo

In order to resolve failed test: https://travis-ci.org/coreos/prometheus-operator/jobs/411752894
---
 examples/etcd.jsonnet | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/examples/etcd.jsonnet b/examples/etcd.jsonnet
index 871f5747..c8687c89 100644
--- a/examples/etcd.jsonnet
+++ b/examples/etcd.jsonnet
@@ -13,13 +13,13 @@ local kp = (import 'kube-prometheus/kube-prometheus.libsonnet') +
       //  * https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#endpoint (has tlsConfig)
       //  * https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#tlsconfig (has: caFile, certFile, keyFile, serverName, & insecureSkipVerify)
 
-      // Set these three variables to values that are valid to scrape etcd metrics with (check the apiserver container).
+      // Set these three variables to the fully qualified directory path on your work machine to the certificate files that are valid to scrape etcd metrics with (check the apiserver container).
       // Most likely these certificates are generated somewhere in an infrastructure repository, so using the jsonnet `importstr` function can
       // be useful here. (Kube-aws stores these three files inside the credential folder.)
       // All the sensitive information on the certificates will end up in a Kubernetes Secret.
-      clientCA: importstr '/path-on-your-work-machine/etcd-client-ca.crt',
-      clientKey: importstr '/path-on-your-work-machine/etcd-client.key',
-      clientCert: importstr '/path-on-your-work-machine/etcd-client.crt',
+      clientCA: importstr 'etcd-client-ca.crt',
+      clientKey: importstr 'etcd-client.key',
+      clientCert: importstr 'etcd-client.crt',
 
       // A valid name (DNS or Subject Alternative Name) that the client (i.e. prometheus) will use to verify the etcd TLS certificate.
       serverName: 'etcd.my-cluster.local', // a real-life e.g. value is "etcd.kube-system.svc.cluster.local"
-- 
GitLab