Ability to add FQDN along with IP address in existing clusters for the API server

If the kubeconfig file is changed to have server entry from IP to FQDN

server: https://baas-stage0-vip.juniper.net

Kubectl fails with the following error

Unable to connect to the server: x509: certificate is valid for kubernetes-master, kubernetes, kubernetes.default, kubernetes.default.svc, kubernetes.default.svc.cluster.local,, 10, apiserver, 
not baas-stage0-vip.juniper.net

it would be great to be able to update the cluster after its built to allow users to conenct via a FQDN and IP.

  • Guest
  • Jun 1 2021
  • Planned
  • Attach files