-
Notifications
You must be signed in to change notification settings - Fork 253
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add additional description for DNS #497
Conversation
I am working on my env and noticed that the new VM is not able to start because my VM can't talk to openstack URL (which is web URI instead of IP), so we need guide user to create this DNS explicility.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jichenjc The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hm I'm a little bit confused when exactly this property is needed. I wasn't even aware the property exists until now and I did not set it in any of my clusters. (I'm also accessing OpenStack via URL not IP) |
it's needed. here's the reason :) the network is created by our logic so if we pass the DNS param, the /etc/resolv.conf of openstack deployed VM will be updated to include the DNS location , my openstack URL is abc.com (different, but like this), not IP ,so when the kubeadm start, because it's openstack cloud provider, it's trying to reach the URL to get additional info, if the DNS is not set, then the URL might not be recognized so that the kubeadm/kubelet is not able to correctly start |
@jichenjc Never mind. I'm actually setting this property and forgot that I did :) That explains why it works in my env /lgtm |
/test pull-cluster-api-provider-openstack-test |
I am working on my env and noticed that the new VM is not able to start because my VM can't talk to openstack URL (which is web URI instead of IP), so we need guide user to create this DNS explicility.
I am working on my env and noticed that the new VM is not able to
start because my VM can't talk to openstack URL (which is web URI
instead of IP), so we need guide user to create this DNS explicility.
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
Release note: