kops: DNS record for public API address not updated
-
What
kopsversion are you running? The commandkops version, will display this information. 1.9.1 1.9.0 -
What Kubernetes version are you running?
kubectl versionwill print the version if a cluster is running or provide the Kubernetes version specified as akopsflag. 1.9.3 1.9.9 -
What cloud provider are you using? AWS
-
What commands did you run? What is the simplest way to reproduce this issue? Create cluster with
--networking amazon-vpc-routed-eni. -
What happened after the commands executed? Cluster comes up, but the DNS record for the API is never updated. i.e. api.xxx.xxx The records pointing to the internal IP addresses for components are updated correctly. i.e.
api.internal.xxx.xxx,etcd-b.internal.xxx.xxxandetcd-events-b.internal.xxx.xxx.
In addition validate also detects the problem:
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.
-
What did you expect to happen? The API DNS record is updated to resolve to the public IP address of a master node.
-
Please provide your cluster manifest. Execute
kops get --name my.example.com -o yamlto display your cluster manifest. You may want to remove your cluster name and other sensitive information. https://gist.github.com/fernandesnikhil/8bb89f76976728f74d53b287420f4011 -
Please run the commands with most verbose logging by adding the
-v 10flag. Paste the logs into this report, or in a gist and provide the gist link here.kops createandkops updatelogs for a cluster with this problem: https://gist.github.com/fernandesnikhil/caed532e79d08a81013f489ece89c561 -
Anything else do we need to know? Tried with the following versions: kops 1.9 and kubernetes 1.9.3 kops 1.9.1 and kubernetes 1.9.3, 1.9.9
DNS records are updated fine when using --networking calico
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 2
- Comments: 32 (6 by maintainers)
Stuff like this happening in kops scares me and EKS is $0.2/hr… Hello @gcp!
Anyone experiencing this with kops 1.17? I see some mentioned of awfully small instance types. This could cause some pods to be stuck pending because they don’t fit on any nodes.
@fejta-bot: Closing this issue.
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle rotten.Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close
Stale issues rot after 30d of inactivity. Mark the issue as fresh with
/remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.If this issue is safe to close now please do so with
/close.Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten
Issues go stale after 90d of inactivity. Mark the issue as fresh with
/remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.If this issue is safe to close now please do so with
/close.Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
I installed the release-1.12 branch and it seems to be working fine now. I also changed the AWS region from us-east-1a to us-east-1d