-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Proposed roadmap to 1.0 #838
Conversation
LGTM! |
Please hold off on committing this for a few workdays to gather feedback :) On Fri, Aug 8, 2014 at 4:03 PM, Daniel Smith notifications@github.com
|
This document is intended to capture the set of features, docs, and patterns that we feel are required to call Kubernetes “feature complete” for a 1.0 release candidate. This list does not emphasize the bug fixes and stabilization that will be required to take it all the way to production ready. This is a living document, and is certainly open for discussion. | ||
|
||
## APIs | ||
1. Versioned APIs: Manage APIs for master components and kubelets with explicit versions, version-specific conversion routines, and component-to-component version checking. |
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.
nit: Can you make these incrementing numbers so that it's reference able (#6 of APIs) without markdown rendering?
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.
Done
On Fri, Aug 8, 2014 at 4:38 PM, Clayton Coleman notifications@github.com
wrote:
In docs/roadmap.md:
@@ -0,0 +1,72 @@
+# Kubernetes Roadmap
+
+Updated August 8, 2014
+
+This document is intended to capture the set of features, docs, and patterns that we feel are required to call Kubernetes "feature complete" for a 1.0 release candidate. This list does not emphasize the bug fixes and stabilization that will be required to take it all the way to production ready. This is a living document, and is certainly open for discussion.
+
+## APIs
+1. Versioned APIs: Manage APIs for master components and kubelets with explicit versions, version-specific conversion routines, and component-to-component version checking.nit: Can you make these incrementing numbers so that it's reference able (
#6 #6 of APIs)
without markdown renderingLReply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/838/files#r16021918
.
One thing that I think is important and I'm not sure if it's covered above or not, is that there's no reverse communication path from kubelet to apiserver for things like errors starting pods. |
There is a line item under "Global features" for error propagation. On Fri, Aug 8, 2014 at 5:26 PM, Daniel Smith notifications@github.com
|
Ah, perfect. Missed that. |
I'm impressed that your roadmap broke the build :P |
Anyone else has comments? I'm going to commit this afternoon On Fri, Aug 8, 2014 at 9:38 PM, Clayton Coleman notifications@github.com
|
LGTM |
Add custom metrics to spec.
update the status of kustomize subcommand integration kep
No description provided.