Update Monitoring external etcd.md

This commit is contained in:
naseemkullah authored and GitHub committed 2018-04-22 22:31:04 -04:00
1 parent 26d1dc86c9
commit 754ba95991
1 file changed
+1 -1
+1 -1
View File
@@ -46,7 +46,7 @@ If your Prometheus Operator is already in place, update it:
The below manifest creates a Service to expose etcd metrics (port 2379)
* Replace I`P_OF_YOUR_ETCD_NODE_[0/1/2]` with the IP addresses of your etcd nodes. If you have more than one node, add them to the same list.
* Replace `IP_OF_YOUR_ETCD_NODE_[0/1/2]` with the IP addresses of your etcd nodes. If you have more than one node, add them to the same list.
* Use `#insecureSkipVerify: true` or replace `ETCD_DNS_OR_ALTERNAME_NAME` with a valid name for the certificate.
In case you have generated the etcd certificated with kube-aws, you will need to use insecureSkipVerify as the valid certificate domain will be different for each etcd node (etcd0, etcd1, etcd2). If you only have one etcd node, you can use the value from `etcd.internalDomainName` speficied in your kube-aws `cluster.yaml`