Enable v1beta3 API via --runtime_config=api/v1beta3 flag

This exposes the proper v1beta3 API endpoint when the user specifies the --runtime_config=api/v1beta3 argument to the apiserver. v1beta3 is still considered experimental and subject to change.

--runtime_config is a map of string keys and values, that can be specified by providing

    --runtime_config=a=b,b=c,d,e

Only the key must be specified, the value can be omitted.

Enables v1beta3 in hack/local-up-cluster.sh and hack/test-cmd.sh

@bgrant0607

Will allow completion of remaining #1519 items
Treating the flag as "present" to enable.  Might be overkill or too clever, but means we don't have to define true/1/yes semantics for a label.  We could treat this as a label set and use label semantics, but I imagine we'll want values broader than the label subset.


> On Dec 11, 2014, at 7:30 PM, bgrant0607 <notifications@github.com> wrote:
> 
> In hack/local-up-cluster.sh:
> 
> > @@ -92,6 +92,7 @@ APISERVER_LOG=/tmp/kube-apiserver.log
> >    -v=${LOG_LEVEL} \
> >    --address="${API_HOST}" \
> >    --port="${API_PORT}" \
> > +  --runtime_config=api/v1beta3 \
> No value necessary when the option is a bool?
> 
> —
> Reply to this email directly or view it on GitHub.
>