kops: api and api.internal dns doesn't replace 203.0.113.123

kops version: Version 1.5.3

Kubernetes: kubernetesVersion: 1.5.2

Provider AWS.

I followed https://github.com/kubernetes/kops/blob/master/docs/aws.md.

Worked in the past with 1.4.8 k8s version and kops 1.4.4.

I’m miss something?

Thanks in advance

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 1
Comments: 35 (12 by maintainers)

Most upvoted comments

I am going to close as you got past the problem with the latest release, please reopen if you need to.

+15

chrislovecnm on May 20, 2017

Issue is happening in 1.9.0

+10

john-delivuk on Apr 26, 2018

Confirming that kops cannot boot up and change the k8s API DNS records with a t2.nano master and a t2.nano node. Changing both to t2.micro got kops validate cluster working within one minute.

charklewis on May 24, 2018

Guys i got some success by delegating a zone , so it is resolvable from the TLDs.

Basically the name of the cluster has to be resolvable from the TLDs , i hope that makes sense.

bechampion on Jun 8, 2018

I figured out what was causing my problem.

I was telling the system to use t2.nano machine sizes. I am going to wager that if i dug into those machines a little deeper i would have likely seen resource fatigue… or some other reason the machine failed to make it to the DNS A record set for the api and api internal binding… related to machine size.

Just to confirm this I set it back to use nano machines over night and let it run all night. It did not complete. Prior to leaving the office yesterday I was tinkering with the configs assuming that perhaps one of my configs may be damaging this. I had those settings off, and it did come in after about 10 minutes.

Hypnocrit on Oct 26, 2017