[WIP] Add support for applying a Config with set of resources via kubecfg

Discussion: https://github.com/GoogleCloudPlatform/kubernetes/issues/1905
One reason to define an object was to allow server side objects to return config (we have an endpoint /templateConfigs that you POST a Template to and get a Config back).  Config as a general concept shouldn't have to depend on the api.Config object as you noted, just allows input earlier in the config pipeline.

----- Original Message -----
> > +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> > +See the License for the specific language governing permissions and
> > +limitations under the License.
> > +*/
> > +
> > +package v1beta1
> > +
> > +import (
> > +	kubeapi "github.com/GoogleCloudPlatform/kubernetes/pkg/api/v1beta1"
> > +	"github.com/GoogleCloudPlatform/kubernetes/pkg/runtime"
> > +)
> > +
> > +// Config contains a set of Kubernetes resources to be applied.
> > +// TODO: Unify with Kubernetes Config
> > +//       https://github.com/GoogleCloudPlatform/kubernetes/pull/1007
> > +type Config struct {
> 
> What is the rationale for modeling a client-side concept similar to API
> objects? Why not just a JSON list containing the objects? What is the
> consumer of this metadata?
> 
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/GoogleCloudPlatform/kubernetes/pull/1958/files#r19258014