JenTing

Thanks @innobead pointing out :bow: @Martin-Weiss I'm wondering if the user would like to change ETCD server SAN to FQDN at day-2 operation.

@Martin-Weiss Question: would it be possible that different etcd server with different FQDN? Like - etcd-server-1: FQDN=etcd-server1 - etcd-server-2: FQDN=etcd-server2 - etcd-server-3: FQDN=etcd-server3 Currently evaluation is it's doable by -...

@Martin-Weiss Thanks for the explanation, so the expected etcd SAN should be like this: etcd-server-1: FQDN=etcd-server1.. etcd-server-2: FQDN=etcd-server2.. etcd-server-3: FQDN=etcd-server3... Correct me if I’m wrong.

I can't find a way to fulfills each ETCD server's have its short/FDQN as SAN. All I could find now is all ETCD servers use the same short/FQDN as SAN....

Ref to https://github.com/coreos/etcd-operator/issues/901

> At the moment ETCD is using a server.crt which per default only has the IP address of the master node it is running on. > > In case we...

> Not sure what commands you are asking for - basically I just checked the certificates with openssl. > > openssl s_client -connect .... |openssl x509 -noout -text.. I think...

I encountered into a problem, my cluster is bootstrap by IP address and I'd like to access ETCD servers by its hostname so my Prometheus scrape config would like this:...

> I encountered into a problem, my cluster is bootstrap by IP address and I'd like to access ETCD servers by its hostname so my Prometheus scrape config would like...

@mdnix 👋 thanks for your feedback. It's the historic reason that Velero set the default cpu/memory requests/limits. Please refer to the [issue](https://github.com/vmware-tanzu/velero/issues/3234). Perhaps, we should only set the default cpu/memory...