WIP: First cut at input validation for Kubelet

* Add some util functions for basic validation
* Spec api fields more tightly
* Break a dep from util -> api, so I can do the reverse
* Add functions to validate structures
* Call those functions when running manifests

This does not validate as it unmarshals YAML or JSON because I want to be able
to validate structures that come from other inputs without forcing them to be
YAML.

This does not handle all api structures - I am not familiar wnough with the
rest to spec them this tightly - I hope someone else can do that.

There are a number of open questions, marked "FIXME".  Please offer feedback
or opinions.
Added compat - running e2e now


On Sun, Jun 29, 2014 at 1:22 PM, Daniel Smith <notifications@github.com>
wrote:

> In api/examples/pod-list.json:
>
> > @@ -8,6 +8,8 @@
> >              },
> >              "desiredState": {
> >                "manifest": {
> > +                "version": "v1beta1",
> > +                "id": "my-pod-1",
>
> Yeah, different change is fine. Sorry, I edited my comment but I think
> that's not reflected in the mail you responded to. I'll just repeat the bit
> I added:
>
> I suspect that at least the guestbook example requires this modification
> as well. I'll be surprised and unhappy if hack/e2e-test.sh passes without
> some modifications there, too.
>
> --
> Reply to this email directly or view it on GitHub
> <https://github.com/GoogleCloudPlatform/kubernetes/pull/280/files#r14331296>
> .
>