kops: Placeholder IP not getting resolved(Spotinst - Kops)
Following up with this guide " [http://blog.spotinst.com/2017/08/17/elastigroup-kubernetes-operations-kops/]
I’m setting up a new cluster using spotinst provider but not able to connect to the api server , commands are failing with what looks like the common “placeholder IP” address error. `$kops validate cluster
cannot get nodes for “example.xyz.co”: Get https://api.example.xyz.co/api/v1/nodes: net/http: TLS handshake timeout
$ kubectl get nodes Unable to connect to the server: net/http: TLS handshake timeout`
I’ve checked that my 4 DNS NS entries matches the 4 entries provided by my Route53 Hosted Zone. It’s been several hours, so DNS should have replicated.
Again, I can see the 3 nodes (Running) in the EC2 console (nodes.MY_CLUSTER), which correspond to my config.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 20
Am getting the below error while executing kops validate cluster command. Also public IP is not updating in Route53. How to fix this?
VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed
The dns-controller Kubernetes deployment has not updated the Kubernetes cluster’s API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.
Validation Failed
@vidurgupta I believe you should create an issue at the fork repository because spotinst provider isn’t supported by the official version yet: https://github.com/spotinst/kubernetes-kops