Also, how do we find the actual values that we put in for the `[127.0.0.1]` sect . . .

Kubernetes
#1

Joe:
Also, how do we find the actual values that we put in for the [127.0.0.1] section above?

#2

Ravan Nannapaneni:
https://kubernetes.io/docs/tasks/administer-cluster/configure-upgrade-etcd/#backing-up-an-etcd-cluster

#3

Ravan Nannapaneni:

ETCDCTL_API=3 etcdctl --endpoints=<https://127.0.0.1:2379> \
  --cacert=&lt;trusted-ca-file&gt; --cert=&lt;cert-file&gt; --key=&lt;key-file&gt; \
  snapshot save &lt;backup-file-location&gt;
#4

Joe:
Thanks Ravan - unfortunately that doesnt answer my question

#5

Mani:
If you are running etcdctl utility from the server where etcd is present then you can use address [127.0.0.1] and the port 2379 where etcd is listening.
if etcd is running on different server(say 10.10.0.1), you can mention that server ip and the port of etcd like this https://[10.10.0.1]:2379

#6

Rocky:
Please look Client url flag in etcd.yaml

#7

Fernando Jimenez:
@Joe If the etcd is implemented as a pod running in the controlplane and you have access to the controlplane filesystem, you might find the information under /etc/kubernetes/manifest/etcd.yaml
Also, the information can be extrapolated from a kubectl -n kube-system describe pod etcd-controlplane in the command section. It will show as --listen-client-urls=