Proposal: Describe possible project structure and implications

Initial thoughts around scoping Kubernetes resources to projects and the associated implications.

Intended as a complement to #891, but with more detail on the implementation consequences of project scoping throughout the stack.

Would like to get general agreement on an outline to proceed against to support an initial prototype in next couple weeks.
I enumerate both for transparency so it's clear that an admin may create it but it's meant to be read by an end user.  

Sent from my iPhone

> On Aug 27, 2014, at 4:54 PM, erictune <notifications@github.com> wrote:
> 
> In docs/projects.md:
> 
> > +* Ensure it provides a pattern to easily add new project scoped resources as extensions to core
> > +* Ensure it is efficient at desired project scale limits
> > +
> > +## Use cases
> > +
> > +Actors:
> > +
> > +1. k8s admin - administers a kubernetes cluster
> > +2. k8s user - uses a kubernetes cluster to schedule pods
> > +
> > +Initial:
> > +
> > +1. Ability for a k8s admin to create projects
> > +2. Ability for a k8s admin to delete projects
> > +3. Ability for a k8s user to list projects
> > +4. Ability for a k8s user to get a project
> are 1 and 4 basically the same?
> 
> —
> Reply to this email directly or view it on GitHub.