-
Notifications
You must be signed in to change notification settings - Fork 155
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 different roles for worker nodes & the control plane #3995
Conversation
/retest |
/assign @alvaroaleman |
6e2566b
to
43ba204
Compare
api/pkg/crd/kubermatic/v1/cluster.go
Outdated
RouteTableID string `json:"routeTableId"` | ||
InstanceProfileName string `json:"instanceProfileName"` | ||
SecurityGroupID string `json:"securityGroupID"` | ||
|
||
AvailabilityZone string `json:"availabilityZone"` |
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.
Why did you re-add this? @kdomanski deliberately remvoved it in #3986
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.
I screwed up the merge 🤦♂️
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.
Gone with 564566e
/lgtm |
LGTM label has been added. Git tree hash: cf8160ccd84596054de1f21ffbe9c032a3034c7c
|
/assign @zreigz |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alvaroaleman, zreigz 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 |
What this PR does / why we need it:
This PR will make sure that we:
I decided against creating new API credentials as that would not make any improvement, since the control plane does a assume-role.
Fixes #3716
Does this PR introduce a user-facing change?: