Proposal: v1beta3 API overhaul

Speculative change for some items from #1200:

* Metadata that applies to resources is split from APIMetadata on non-resource API objects
* Metadata is a sub field of objects
* Labels are on Metadata
* Pod current and desired state is split
* Name is used for pods instead of ID (UID is part of metadata, Name is part of resource) for idempotent creation #148 and #1216 
* PodTemplate is a Metadata carrying object as per #170
 * If replicationController gave way to a generic "replicator", then pod template could be both a nested struct and a real resource.
* A ScheduledPod and ScheduledPodList is what the kubelet sees as per #860
* Non-schema'd k/v values on Metadata as `Config` (better names welcome) as per #1201

Not changed yet:

* ReplicationControllers
* Services

EDIT: Moving to higher bandwidth document here: https://docs.google.com/document/d/1E_HNsbyocweD9zJHXbz5Xb9XPwBqvDnLHhGeBq15FlI/edit?usp=sharing
Yes - PodTemplate has PodTemplateSpec, ReplicationController has a ReplicationControllerSpec with a PodTemplateReference (or just ComponentReference).

----- Original Message -----
> >  }
> >  
> > -func (*Pod) IsAnAPIObject() {}
> > +// PodTemplateSpec describes the data a pod should have when created from
> > a template
> > +type PodTemplateSpec struct {
> > +	// Metadata of the pods created from this template.
> > +	Metadata ObjectMeta `json:"metadata,omitempty" yaml:"metadata,omitempty"`
> 
> Got it.  Is this true after we decouple template from replication?
> 
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/GoogleCloudPlatform/kubernetes/pull/1225/files#r18055920