11 Commits (b1a9e81e1faab58d9c6c7b724ee0ba71a289b97f)

Author	SHA1	Message	Date
Wojciech Tyczynski	82f565e3ea	Change performance targets	2015-03-26 07:43:22 +01:00
David Oppenheimer	0e1c0b26dc	Update roadmap.md	2015-02-17 23:09:45 -08:00
Tim Hockin	39e63d94fc	First draft of roadmap to 1.0 update	2015-02-09 16:09:41 -08:00
kargakis	3006bd70b0	Fix roadmap doc	2015-01-31 20:53:27 +01:00
Satnam Singh	d1ccfd81c7	Add performance roadmap items	2015-01-27 12:20:23 -08:00
Brian Grant	1ed9597975	First draft of CLI/config roadmap.	2015-01-22 18:18:46 +00:00
Satnam Singh	66b334f308	Start to incorporate reliability work items into roadmap	2015-01-05 13:59:08 -08:00
Brian Grant	5ef877e914	Update roadmap based on discussion at contributor meetup.	2014-12-08 18:54:34 +00:00
Tim Hockin	ee2df8683c	Update roadmap ... We took a hard look at 1.0 and what things ae really REQUIRED to get to a stable release that is "useful". This required moving some things we thought were really important but not CRITICAL down the list. For now they are stricken from this doc, but I expect this doc to start growing a "post 1.0" list soon. Things stricken and why: Using the host network: This is primarily a performance optimization, but it causes potential problems with other uses of HostPorts. We'd rather focus on fixing perf problems than dodging them. We can revisit later if there is a strong case for it. Representation of Ports in the Manifest structure: We discussed and decided that, since HostPort semantics have changed, this matters less than before. Scenarios where IP-per-pod is hard or impossible: We're still game to help people figure out how to make it work, but we don't see a case for making k8s 1.0 work in a fundamentally different mode. Too much churn and risk. We can revisit later, if needed. Auto-scaling controller: We really want this, but it's not critical to making k8s "useful". Pluggable authentication: Overlaps with the other identity topic. Having one topic seems clearer. Pod spreading: We still want this, but it's not critical for 1.0. Container status snippets: We still want this, but it's not critical for 1.0. Docker-daemon-kills-all-children-on-exit problem: This is still a big problem, but we're not going to gate our 1.0 on something we don't control. This has to be documented as a shortcoming in general. Interconnection of services: expand / decompose the service pattern: overlaps with the other services topic. Recipes for settings where networking is not like GCE: This is happening in the form of cloudprovider modules, but is not going to gate 1.0.	2014-08-28 12:42:22 -07:00
Brendan Burns	c1b9ea3aad	Update the roadmap with some completed tasks.	2014-08-25 20:14:36 -07:00
Tim Hockin	b5d55c1702	Proposed roadmap to 1.0	2014-08-11 15:18:55 -07:00