-
Notifications
You must be signed in to change notification settings - Fork 31
Api server is not up and running #63
Comments
Did you provide the correct the DNS credentials for Route53? |
I had the similar issue, all vms running well and from the inside of master node, i could see the errors to call openstack api. OpenStack in my environment is setup with self-signed certificates, and I also upload the |
@afritzler my issue now is the etcd pod not running, leading to the the api-server in master node failed tried change this value to could you help on this ? |
Don't set the I need to look into the Designate support. |
/cc @mandelsoft |
Hello,
I am using OpenStack IaaS provider and I set up the terraform script accordingly through the guide on the official wiki. However after successful execution of "terraform apply variant" the commands "k8s/bin/k" are returning Unable to connect to the server: EOF.
I was also not able to use kubectl by directly using the floating IP of either load balancer or master node
Here is my tfvars file
The text was updated successfully, but these errors were encountered: