-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
📖 Managed Kubernetes in CAPI proposal #6988
📖 Managed Kubernetes in CAPI proposal #6988
Conversation
As discussed during 8/3/22 office hrs, could the reviewers take another look at it? @richardcase and I addressed most comments in the initial google doc and moved to this PR. cc @alexeldeib, @CecileRobertMichon, @enxebre, @fabriziopandini, @jackfrancis, @sbueringer, @yastij |
@joekr, @shyamradhakrishnan, could you also review the proposal as you are looking into managed k8s implementation for OCI provider? |
thanks @pydctw looks great, dropped some comments. |
9a1b9b7
to
2acf17a
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.
looks good from my side
/lgtm
Thanks @sbueringer - i'm on it 👍 |
aef5139
to
52a0077
Compare
Thank you! /lgtm |
|
||
#### Story 3 | ||
|
||
As a cluster admin, |
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'd say this is a service consumer story, a cluster admin does not necessarily cares how a cluster was provisioned, they just have admin rbac.
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.
Agree that it is a service consumer story for managed Kubernetes. I left it as a cluster admin story as the user wants to provision both “unmanaged” and “managed” Kubernetes clusters and for "unmanaged" cluster, they will need a cluster admin role. Thoughts?
Can we please squash commits? |
52a0077
to
478615a
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Co-authored-by: Richard Case <[email protected]> Co-authored-by: Winnie Kwon <[email protected]>
478615a
to
f914d18
Compare
We added new commits to address comments for easy reviewing but now that most of the comments are addressed, squashed the commits. |
We reached lgtm quorum from reviewers, lazy consensus until Friday August 26th starting now |
/lgtm I assume #6988 (comment) is non-blocking and can be addressed in a follow-up if necessary. |
/lgtm |
The lazy consensus deadline passed. Could we merge the PR? cc @sbueringer @fabriziopandini |
Yes! /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer 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 |
Thx @pydctw & @richardcase for pushing this forward!! 🎉 |
What this PR does / why we need it:
This proposal discusses various options on how managed Kubernetes services could be represented in Cluster API by providers and makes a recommendation for new implementations. One of main goals/motivation of the proposal is to reach a consensus on how
ClusterClass
should be supported for managed Kubernetes by agreeing on the API option.cc @richardcase
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 #6126