Tej_Singh_Rana:
Can you please reverify the steps?
Sunil Sharma:
i just followed the steps as documented and in videos
, i was on Bootstrapping the Kubernetes Control Plane section
Tej_Singh_Rana:
Please share the output of below command:
sudo systemctl cat kube-apiserver.service
Tej_Singh_Rana:
sudo systemctl status kube-apiserver
Tej_Singh_Rana:
can you please verify all certs and keys moved in that location /var/lib/kubernetes
successfully?
Sunil Sharma:
i have installed etcd - 3.3.9
and Kubectl - 1.19.0
Sunil Sharma:
I manage to fix the kube-api server by changing --runtime-config=api/all=true
Sunil Sharma:
@Tej_Singh_Rana @Mohamed Ayman Now getting this error
Unable to connect to the server: x509: certificate is valid for 192.168.5.11, 10.0.0.1, not 127.0.0.1
Sunil Sharma:
@Mohamed Ayman can you help on this
Unable to connect to the server: x509: certificate is valid for 192.168.5.11, 10.0.0.1, not 127.0.0.1
Sunil Sharma:
@Miroslav Karanovic try this kube-api server by changing etc/systemd/system/kube-apiserver.service --runtime-config=api/all=true
Sunil Sharma:
@Mumshad Mannambeth can you pls help with error i am facing ?
Unable to connect to the server: x509: certificate is valid for 192.168.5.11, 10.0.0.1, not 127.0.0.1
Miroslav Karanovic:
I have solved the problem on Master-1 so far, if there are no other problems. I am not have IP address --advertise-address=192.168.5.11 in kube-apiserver.service, but I still have a similar problem on worker-2 node for TLS bootstraping.
Sunil Sharma:
Can you share your kube-apiserver. Service?