-
Notifications
You must be signed in to change notification settings - Fork 260
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 providerID #274
Add providerID #274
Conversation
5117d94
to
a576674
Compare
need upgrade cluster-api....... |
/hold Just to not being merged accidentally. As @jichenjc mentioned... we need an update of cluster-api for this. With having this, we might want to remove the annotation |
@chrigl can you share how to upgrade cluster-api? seems change the master branch to latest commit doesn't help, should we wait for a release of cluster-api? |
@jichenjc We keep the master branch of |
[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 |
refer to aws implementation, add providerID in exists function
@chrigl because we already updated the cluster-api to branch 0.1.0 , we can remove the /hold flag here? Thanks |
I plan to update kubernetes/autoscaler#1866 so that mapping between nodes and machines relies solely on the ProviderID being set -- this PR would help that goal. |
What's the hold up on merging this? |
we should already have this provider ID in latest code already |
refer to aws implementation, add providerID in exists function
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: