-
Notifications
You must be signed in to change notification settings - Fork 132
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
Implement ProviderID() for Anexia #1385
Conversation
Hi @LittleFox94. Thanks for your PR. I'm waiting for a kubermatic member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
Signed-off-by: Mara Sophie Grosch <[email protected]>
2f6c6a8
to
98ff0be
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
LGTM label has been added. Git tree hash: 0ece001ee20db5855be763460668e5c8000ec6c6
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: LittleFox94, moadqassem, xmudrii 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 |
Thanks for fast approval! You can always ping me for Anexia stuff btw :) |
/retest Review the full test history Silence the bot with an |
What this PR does / why we need it:
#1351 changed the mapping from Machine to Node, but left the
ProviderID()
method unimplemented for Anexia, this adds the implementation.Special notes for your reviewer:
Our CCM currently does not set any prefix, which I guess could make problems when having a single cluster spanning multiple providers. At least they are fairly long and random, so chance for collision isn't too high .. still, if you need us to change that, I'll happily find a way for that.
Probably would make the most sense if @xmudrii takes a look at this, as I took that named TODO ^^'
Optional Release Note: