Roadmap Updates

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.

See the commit comments for details.


Will do


On Thu, Aug 28, 2014 at 10:34 AM, Joe Beda <notifications@github.com> wrote:

> In docs/roadmap.md:
>
> > -  2. Representation of Ports in the Manifest structure
> > -  3. Utility of HostPorts in ip-per-pod
> > -  4. Scenarios where IP-per-pod is hard or impossible
> > -  5. Port collisions between services
> > -9. Provide a model for durable local volumes including scheduler constraints.
> > -10. Auth[nz] and ACLs: Have a plan for how identity, authentication, and authorization will fit in to the API, as well as ACLs for objects, and basic resource quotas.
> > -  1. Projects / subdivision: Have a plan for how security isolation between users could apply in terms of grouping resources (calling out explicitly) and whether there is a common model that could apply to Kubernetes
> > -
> > +2. Component-centric APIs:  Clarify which types belong in each component's API and which ones are truly common.
> > +  1. Clarify the role of etcd in the cluster.
> > +3. Idempotency: Whenever possible APIs must be idempotent.
> > +4. Container restart policy: Policy for each pod or container stating whether and when it should be restarted upon termination.
> > +5. Life cycle events/hooks and notifications: Notify containers about what is happening to them.
> > +6. Re-think the network parts of the API: Find resolution on the the multiple issues around networking.
> > +  1. ~~Utility of HostPorts in ip-per-pod~~ **Done**
> > +  2. Services/Links/Porals/Ambassadors
>
> portals
>
> --
> Reply to this email directly or view it on GitHub
> <https://github.com/GoogleCloudPlatform/kubernetes/pull/1084/files#r16854827>
> .
>