-
Notifications
You must be signed in to change notification settings - Fork 77
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
update mcm to use worker secret ref. for the machine class credentialsSecretRef #230
update mcm to use worker secret ref. for the machine class credentialsSecretRef #230
Conversation
2c1f0ec
to
6cc0aa2
Compare
6cc0aa2
to
f678e66
Compare
/status author-action |
@danielfoehrKn The pull request was assigned to you under |
f678e66
to
9675adc
Compare
9675adc
to
22d7fa4
Compare
22d7fa4
to
58a6d1f
Compare
58a6d1f
to
f5d67e3
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
Nice PR.
/rebase |
f5d67e3
to
3025486
Compare
@danielfoehrKn can you run |
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.
/invite @prashanth26
/assign @prashanth26
3025486
to
80ab3f7
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
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
How to categorize this PR?
/area quality
/kind enhancement
/priority normal
/platform azure
What this PR does / why we need it:
Uses the machine classes .{spec.}credentialsSecretRef field. It is a reference to a secret containing only the credentials, while today's .{spec.}secretRef still contains the user-data. See here for more details.
Uses the worker's secret reference as the credentialsSecretRef.
This means all worker pools use the same "cloudprovider" secret containing only the cloud provider credentials.
The existing MachineClass SecretReference then only contains the user data that is different for each pool.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note: