podex: initial import

podex is a command line tool to bootstrap a kubernetes container manifests from docker image metadata.

Manifests can then be edited by a human to match deployment needs.

Example usage:
```
$ docker pull google/nodejs-hello
$ podex -yaml google/nodejs-hello > google/nodejs-hello/pod.yaml
$ podex -json google/nodejs-hello > google/nodejs-hello/pod.json
```

The `podex/manifests` subdirectory could also be used to host example pods for popular docker images.
Are you intending this as a tool people can use, or as an actual
collection?  I'm OK with a tool, I think collecting pod specs is a
different discussion.  I'd be inclined to drop the manifests dir, and just
leave teh tool, for now.

On Thu, Oct 2, 2014 at 10:25 AM, Johan Euphrosine <notifications@github.com>
wrote:

> In podex/manifests/google/nodejs-hello/pod.json:
>
> > @@ -0,0 +1,19 @@
> > +{
> > +  "version": "v1beta1",
> > +  "id": "nodejs-hello-pod",
> > +  "volumes": null,
> > +  "containers": [
> > +    {
> > +      "name": "nodejs-hello",
> > +      "image": "google/nodejs-hello",
> > +      "ports": [
> > +        {
> > +          "name": "nodejs-hello-tcp-8080",
> > +          "hostPort": 80,
>
> I'm not emitting hostport, I just added it manually afterwards.
>
> (The idea behind the manifests subdir was that they would be initially
> generated with the tool, but then manually tweaked by hand).
>
> --
> Reply to this email directly or view it on GitHub
> <https://github.com/GoogleCloudPlatform/kubernetes/pull/1537/files#r18353447>
> .
>