-
Notifications
You must be signed in to change notification settings - Fork 581
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
kube-proxy fails with "--bind-address" flag: x is not a valid IP address seen when not using IP address as node address and cloud provider is configured #1725
Comments
I ran into this issue trying to go from Can I replace DNS hostname with IP value and retry the upgrade or will that mess things up even more? |
putting a IP value for
|
Faced with the same problem. After adding
|
It's a concern, because when using a not resolvable hostname for internal_address, kube-proxy will start with nodeIP 127.0.0.1, causing LoadBalancer service with local externalTrafficPolicy to fail (at least with MetalLB) : metallb/metallb#287 |
I saw this issue in rancher 2.3.3. |
This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions. |
RKE version:
v0.3.2
cluster.yml file:
Steps to Reproduce:
Run
rke up
withcluster.yml
as shown above. (address or internal_address not as IP address and cloud_provider set)Results:
kube-proxy fails to start:
This was implemented because
kube-proxy
fails to start on k8s 1.16 if the IP if not provided to identify the node when cloud-provider is configured (AWS and possibly Openstack)Main problem is that the address still needs to be provided, so we should probably error out in validation or find another way to make this happen. We already concluded not to do DNS resolution in RKE and use the address from that.
Workaround is to use IP addresses and not hostname/fqdn as address.
The text was updated successfully, but these errors were encountered: