-
Notifications
You must be signed in to change notification settings - Fork 1.4k
📖 Managed Kubernetes Feature Group #7546
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 Feature Group #7546
Conversation
Really interesting initiative. cc @joekr /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.
Awesome! I think the base idea is really good - just a little bit unsure as to how this gels with the K8s community definition and processes around working groups:
- https://github.com/kubernetes/community/blob/master/committee-steering/governance/wg-governance.md
- https://github.com/kubernetes/community/blob/master/sig-wg-lifecycle.md
Would it be easier to drop the term "working group" and adopt some similar alternative to keep the lighter-weight process, but avoid confustion between this and a K8s community working group?
Another nit 🙂 - maybe this could go in /docs/community
instead of /docs/proposals
@killianmuldoon good point about the already defined k8s concept of a "working group" (which in my understanding is meant to suggest an inter-team or team-of-teams thing, and less a breakout from one particular team). How about:
|
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.
Thanks for putting this together!
+1 to Killian comments (I kind of like Focus group for the name, but no strong preference)
just added some suggestion, but I think that it is fair also to let the group to work defining deliverables and improving communications patterns over time
e57ac22
to
64407ba
Compare
64407ba
to
4726744
Compare
Looking forward to the inaugural meeting. From my side: /lgtm |
4726744
to
2e29f6f
Compare
@fabriziopandini @sbueringer @killianmuldoon are we willing to consider merging this at this point? |
Great to see this moving |
Thanks @jackfrancis for putting this together. |
/lgtm Thanks for pioneering the feature group! |
Last two open conversations, otherwise I'm fine with merging ASAP. |
2e29f6f
to
f15077b
Compare
@jackfrancis Thank you very much for driving this! Given lgtm's above + only minor changes afterwards /lgtm |
LGTM label has been added. Git tree hash: 587e2cdbb33a6bac7029bf0b18bc44e9bebd35d0
|
[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 |
What this PR does / why we need it:
This PR defines a Working Group to codify where formal conversations and progress is being made in Cluster API for standardizing Managed Kubernetes solutions across the provider ecosystem.
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 #