-
Couldn't load subscription status.
- Fork 5.3k
Creating a Nodeless working group #2215
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
Closed
Closed
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
7cb6383
nodeless wg
6777348
wording change
206e734
new mission statement
7074b38
merging
8ec9567
adding goals and chaning mission statement
45fdd73
Merge branch 'master' into nodeless
rbitia 86992ae
commits
21de9d0
merging
2393ff5
generated files
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,40 @@ | ||
| <!--- | ||
| This is an autogenerated file! | ||
|
|
||
| Please do not edit this file directly, but instead make changes to the | ||
| sigs.yaml file in the project root. | ||
|
|
||
| To understand how this file is generated, see https://git.k8s.io/community/generator/README.md | ||
| --> | ||
| # Nodeless Working Group | ||
|
|
||
| To propose a set of changes to Kubernetes which de-emphasizes the concept of nodes, for users that do not need to be aware of them, and to explore an architectual design for those users. | ||
|
|
||
| ## Meetings | ||
| * Regular WG Meeting: [Wednesdays at 14:00 PT (Pacific Time)](https://zoom.us/j/588409652) (weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=14:00&tz=PT%20%28Pacific%20Time%29). | ||
| * [Meeting notes and Agenda](https://docs.google.com/document/d/13gt9aUokqueOYHzA94D0UXFkXSP0rJEED9TxNEXZZMM/edit?usp=sharing). | ||
|
|
||
| ## Organizers | ||
|
|
||
| * Ria Bhatia (**[@rbitia](https://github.com/rbitia)**), Microsoft | ||
| * Ben Corrie (**[@corrieb](https://github.com/corrieb)**), VMWare | ||
|
|
||
| ## Contact | ||
| * [Slack](https://kubernetes.slack.com/messages/wg-nodeless) | ||
| * [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-wg-nodeless) | ||
|
|
||
| <!-- BEGIN CUSTOM CONTENT --> | ||
| The goals for the working group are as follows: | ||
| Phase 1 | ||
| 1. Define what nodeless Kubernetes means to users, by exploring the realm of use cases | ||
| 2. Design a user experience around nodeless | ||
| 3. Create reference architectures for a nodeless Kubernetes and define clear behaviors for how a nodeless Kubernetes should act | ||
|
|
||
| Phase 2 | ||
| 4. Propose upstream API changes to make Kubernetes more extensible to containers as a service platforms | ||
| 5. Define a clear list of limitations and user impact of nodeless from a user’s point of view | ||
| 6. Propose conformance tests for nodeless kubernetes | ||
| 7. Define a standardized 'nodeless' API/capabilities that we expect nodeless container providers to implement for integration with Kubernetes | ||
|
|
||
|
|
||
| <!-- END CUSTOM CONTENT --> | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Can this be omitted since it presupposes the outcome of phase one? If the goal is inquiry into a solution, that should be the deliverable. Phase 2 cannot be accomplished by a working group. The design from phase one will require consensus building in the affected sub-projects OWNERS in order to get those code changes in (if applicable). WGs do not own code, do not have any vested authority, and are intended to problem solve cross-SIG concerns. The problem is undefined until the work of phase one is complete by design of the WG itself.
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.
@jdumars are you asking us to delete phase two?
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 like the new summary sentence Ria.
The output of the working group should be documentation that explores the domain and comes to detailed recommendations about the alternatives that present themselves. In order to do that, the group will need to:
In that respect, I think (5) is important to keep in scope because any analysis of approaches needs to account for limitations and user impact. (7) matters because a solution can't be credible unless all assumptions are made explicit, but could be rephrased as "document assumptions" rather than a detailed API definition. (4) and (6) seem unnecessary, because I would expect that any upstream changes or compliance questions would be dependent on the solution being accepted.
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 actually don't mind this section. My reading is that "propose" != "implement". Proposals from a WG are fine.
I would drop 7, though. Kubernetes is concerned with the UX and API - any platform that can meet those needs is fine. It's not our place to define what providers need to do.