Skip to content
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

Fix instanceID for vmss nodes #59857

Merged
merged 1 commit into from
Feb 22, 2018
Merged

Conversation

feiskyer
Copy link
Member

What this PR does / why we need it:

When useInstanceMetadata is set to true for vmss nodes, their providerID is wrong.

Their providerID should be in format azure:///subscriptions/<subscription-id>/resourceGroups/<rg-name>/providers/Microsoft.Compute/virtualMachineScaleSets/<scaleset-name>/virtualMachines/<instance-id>.

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 #59855

Special notes for your reviewer:

Release note:

Fix instanceID for vmss nodes.

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Feb 14, 2018
@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 14, 2018
@feiskyer feiskyer added sig/azure and removed approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Feb 14, 2018
@feiskyer feiskyer added this to the v1.10 milestone Feb 14, 2018
@feiskyer feiskyer requested a review from andyzhangx February 14, 2018 08:42
@feiskyer
Copy link
Member Author

/cc @andyzhangx

@feiskyer
Copy link
Member Author

/retest

@jhorwit2
Copy link
Contributor

@feiskyer FYI, you can't update the provider id once it has been set. I imagine that's going to be a problem for existing nodes with the incorrect provider id?

@feiskyer
Copy link
Member Author

@feiskyer FYI, you can't update the provider id once it has been set. I imagine that's going to be a problem for existing nodes with the incorrect provider id?

@jhorwit2 Yep, but please note that vmss is not included in any releases yet. It is a feature for 1.10.

@jberkus
Copy link

jberkus commented Feb 21, 2018

reminder: it is now Code Slush. This PR needs status/approved-for-milestone in order to merge. Thanks.

@feiskyer
Copy link
Member Author

ping @andyzhangx

Copy link
Member

@andyzhangx andyzhangx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 22, 2018
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andyzhangx, feiskyer

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 22, 2018
@feiskyer
Copy link
Member Author

/retest

@k8s-github-robot
Copy link

/test all [submit-queue is verifying that this PR is safe to merge]

@k8s-github-robot
Copy link

Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions here.

@k8s-github-robot k8s-github-robot merged commit 064597a into kubernetes:master Feb 22, 2018
@feiskyer feiskyer deleted the metadata branch February 23, 2018 02:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Node's providerID is wrong for azure vmss when using instance metadata
6 participants