Access.md added.

Some thoughts around identity and access management.  
Ideas still rough, but trying to share early.  Comments welcomed.

Some of this maybe should go into docs/security.md


> On Aug 25, 2014, at 6:21 PM, erictune <notifications@github.com> wrote:
> 
> In docs/access.md:
> 
> > +- `userAccount` object is immutable
> > +- there is no superuser `userAccount`
> > +- `userAccount` objects are statically populated in the k8s API store by reading a config file.  Only a k8s admin can do this.
> > +- `userAccount` can have a default `project`.  If API call does not specify a `project`, the default `project` for that caller is assumed.
> > +- `userAccount` may access multiple projects.
> > +
> > +Improvements:
> > +- Have API calls to create and delete `userAccount`s.
> > +- Make `userAccount` part of a separate API group from core k8s objects like `pod`.  Facilitates plugging in alternate Access Management.
> > +
> > +Simple Profile:
> > +   - single `userAccount`, used by all users.
> > +
> > +Enterprise Profile:
> > +   - every human user has own `userAccount`. 
> > +   - `userAccount`s have labels that indicate both membership in groups, and ability to act in certain roles.
> I'm reconsidering the use of labels in place of groups and roles. Lots of other similar systems have groups and not having them may be confusing for users.
> 

I like the ubiquity of labels and their ability to be defined on everything.  I do feel like a user's role *on* a resource seems difficult to describe with labels and more like a relation.

> —
> Reply to this email directly or view it on GitHub.