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.
I think their info does get slurped back up.


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

> In docs/identifiers.md:
>
> >     Example: "frontend"
> >
> > -8) When starting an instance of a pod on a kubelet, a PodInstanceID (a UUID) will be assigned to that pod instance
> > -   1) If not specified, the kubelet will assign this identifier
> > -   2) If the pod is restarted, it must retain the PodInstanceID it previously had
> > -   3) If the pod is stopped and a new instance with the same PodNamespace and PodName is started, it must be assigned a new PodInstanceID
> > -   4) If the pod is moved across hosts, it must be assigned a new PodInstanceID
> > -   Example: "01234567-89ab-cdef-0123-456789abcdef"
> > +5) When a pod is bound to a node, the node is told the pod's uid.
> > +   1) if not provided, the kubelet will generate one
>
> Are locally created pods visible in the APIserver as API objects? I'm
> guessing not at the moment. In which case, how about just making this doc
> about APIserver object naming, and having a separate "local pods" doc about
> the special cases of node-locally created objects.
>
> --
> Reply to this email directly or view it on GitHub
> <https://github.com/GoogleCloudPlatform/kubernetes/pull/1216/files#r17270915>
> .
>