Revisit identifiers spec

Partially addresses #1135.

This is the result of discussions in the past few days about imprecision and confusion. Hopefully simpler. There are a few FIXME comments in the doc - discuss.
Yes we still need this, I think.  This use of namespace predates the other
form, but I don't really think they are too confusing.  PodNamespace?

The use case here is this.

An apiserver can put a pod named "foo" on a machine.  A config file can put
a pod named "foo" on the same machine.  We can differentiate them as
"etcd.foo" and "file.foo" or something, but then the name that kubelet
reports is not the same as the name in the apiserver.  It seems that we
should be able to re-assemble the information regardless of where it came
from.

Maybe PodNamespace should just be a kubelet-local thing, and if you need to
join data across kubelets and masters you have to use UID?


On Mon, Sep 8, 2014 at 3:13 PM, bgrant0607 <notifications@github.com> wrote:

> In docs/identifiers.md:
>
> >  ## Design
> >
> > -1) Each apiserver has a Namespace string (a DNS_SUBDOMAIN) that is unique across all apiservers that share its configured minions.
> > +1) Each apiserver must be assigned a Namespace string (a DNS_SUBDOMAIN).
>
> Do we still need this?
>
> We should not call this "namespace", since that currently collides with
> the namespace proposal.
>
> Also, in the case of replicated apiservers, they should all share the same
> namespace. So, this is really a type of administrative domain. I suggest
> punting this topic to #1114
> <https://github.com/GoogleCloudPlatform/kubernetes/pull/1114>.
>
> --
> Reply to this email directly or view it on GitHub
> <https://github.com/GoogleCloudPlatform/kubernetes/pull/1216/files#r17270876>
> .
>