Comment 4 for bug 1840214

Revision history for this message
Felipe Reyes (freyes) wrote :

ubuntu@juju-04930e-5:~$ export KUBECONFIG=config
ubuntu@juju-04930e-5:~$ kubectl get pods
Unable to connect to the server: x509: certificate is valid for 192.168.10.211, 192.168.10.211, not 192.168.10.34
ubuntu@juju-04930e-5:~$ grep server config
    server: https://192.168.10.34:443
ubuntu@juju-04930e-5:~$ sed -i s/192.168.10.34/loadbalancer.lan/g config
ubuntu@juju-04930e-5:~$ grep server config
    server: https://loadbalancer.lan:443
ubuntu@juju-04930e-5:~$ host loadbalancer.lan
loadbalancer.lan has address 192.168.10.34
ubuntu@juju-04930e-5:~$ kubectl get pods
No resources found in default namespace.
ubuntu@juju-04930e-5:~$ kubectl get componentstatuses
Unable to connect to the server: x509: certificate is valid for 192.168.10.211, 192.168.10.211, not 192.168.10.34
ubuntu@juju-04930e-5:~$ grep server config
    server: https://192.168.10.34:443
ubuntu@juju-04930e-5:~$ sed -i s/192.168.10.34/loadbalancer.lan/g config
ubuntu@juju-04930e-5:~$ kubectl get componentstatuses
NAME STATUS MESSAGE ERROR
scheduler Healthy ok
controller-manager Healthy ok
etcd-2 Healthy {"health":"true"}
etcd-1 Healthy {"health":"true"}
etcd-0 Healthy {"health":"true"}