Move the internal minion representation to match v1beta3

@ddysher review please, this includes removing the duplicate Labels

Extracted from #1600
Is it the intent we consciously chose?  Probably not.  Is it the way it's used and interpreted in the code?  Yes.


> On Nov 19, 2014, at 8:54 PM, Deyuan Deng <notifications@github.com> wrote:
> 
> In pkg/api/types.go:
> 
> > @@ -637,30 +637,42 @@ type EndpointsList struct {
> >  	Items []Endpoints `json:"items" yaml:"items"`
> >  }
> >  
> > -// NodeResources represents resources on a Kubernetes system node
> > +// NodeSpec describes the attributes that a node is created with.
> > +type NodeSpec struct {
> > +	// Capacity represents the available resources of a node
> > +	Capacity ResourceList `json:"capacity,omitempty" yaml:"capacity,omitempty"`
> > +}
> > +
> > +// NodeStatus is information about the current status of a node.
> > +type NodeStatus struct {
> > +	// Queried from cloud provider, if available.
> > +	HostIP string `json:"hostIP,omitempty" yaml:"hostIP,omitempty"`
> Is "assumes the name resolves" the correct assumption? Just come across this issue #2462. It looks like we never try to query from cloudprovider to populate HostIP.
> 
> —
> Reply to this email directly or view it on GitHub.
>