Skip to content
Snippets Groups Projects
Commit 754ba959 authored by naseemkullah's avatar naseemkullah Committed by GitHub
Browse files

Update Monitoring external etcd.md

parent 26d1dc86
Branches
Tags
No related merge requests found
...@@ -46,7 +46,7 @@ If your Prometheus Operator is already in place, update it: ...@@ -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) 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. * 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` 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`
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment