-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
azure: support nics with multiple ipconfigs #36841
azure: support nics with multiple ipconfigs #36841
Conversation
Jenkins GCI GKE smoke e2e failed for commit 6357c39. Full PR test history. The magic incantation to run this job again is |
Jenkins GCI GCE e2e failed for commit 6357c39. Full PR test history. The magic incantation to run this job again is |
Jenkins Kubemark GCE e2e failed for commit 6357c39. Full PR test history. The magic incantation to run this job again is |
Jenkins GKE smoke e2e failed for commit 6357c39. Full PR test history. The magic incantation to run this job again is |
Jenkins GCE e2e failed for commit 6357c39. Full PR test history. The magic incantation to run this job again is |
Looks like the CI infra is having some problems. This change was validated as working by a colleague. |
LGTM |
@k8s-bot test this please issue: IGNORE (general CI problems) |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue |
What this PR does / why we need it:
When I initially wrote the cloudprovider, the ipconfig primary field either wasn't present or wasn't populated. Now it is and we have someone trying to use kubelet on a node with a nic with multiple ipconfigs and they ran into this.
Which issue this PR fixes: n/a no issue filed.
Special notes for your reviewer:
Release note:
If we can get this backported to 1.4.x, that would be great.
This change is