diff options
| author | Valentin Rothberg <rothberg@redhat.com> | 2019-02-26 14:55:43 +0100 |
|---|---|---|
| committer | Valentin Rothberg <rothberg@redhat.com> | 2019-02-26 15:07:05 +0100 |
| commit | 7fea0d7077cbcbcec1958e31b361009b87e77398 (patch) | |
| tree | fed8e181d02ccde7015461d5dd113c7df1f2077c /docs | |
| parent | 2ce8a1c8906443b7b2a2bfcc44e16f66e8db7cdb (diff) | |
| download | podman-7fea0d7077cbcbcec1958e31b361009b87e77398.tar.gz podman-7fea0d7077cbcbcec1958e31b361009b87e77398.tar.bz2 podman-7fea0d7077cbcbcec1958e31b361009b87e77398.zip | |
docs: cross-reference `podman-{generate,play}-kube`
Addresses: https://github.com/containers/libpod/pull/2428#discussion_r260200694
Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/podman-generate-kube.1.md | 4 | ||||
| -rw-r--r-- | docs/podman-play-kube.1.md | 4 |
2 files changed, 5 insertions, 3 deletions
diff --git a/docs/podman-generate-kube.1.md b/docs/podman-generate-kube.1.md index 5236f23fe..d4bed8ab1 100644 --- a/docs/podman-generate-kube.1.md +++ b/docs/podman-generate-kube.1.md @@ -19,6 +19,8 @@ The **service** option can be used to generate a Service specification for the c if the object has portmap bindings, the service specification will include a NodePort declaration to expose the service. A random port is assigned by Podman in the specification. +Note that the generated Kubernetes YAML file can be used to re-run the deployment via podman-play-kube(1). + # OPTIONS: **s** **--service** @@ -145,7 +147,7 @@ status: ``` ## SEE ALSO -podman(1), podman-container, podman-pod, podman-play +podman(1), podman-container(1), podman-pod(1), podman-play-kube(1) # HISTORY Decemeber 2018, Originally compiled by Brent Baude (bbaude at redhat dot com) diff --git a/docs/podman-play-kube.1.md b/docs/podman-play-kube.1.md index 3fd9746a5..2264f7a88 100644 --- a/docs/podman-play-kube.1.md +++ b/docs/podman-play-kube.1.md @@ -20,7 +20,7 @@ kubernetes_input.yml the pod and containers described in the YAML. The containers within the pod are then started and the ID of the new Pod is output. -Ideally the input file would be one created by Podman. This would guarantee a smooth import and expected results. +Ideally the input file would be one created by Podman (see podman-generate-kube(1)). This would guarantee a smooth import and expected results. # OPTIONS: @@ -72,7 +72,7 @@ $ podman play kube demo.yml ``` ## SEE ALSO -podman(1), podman-container(1), podman-pod(1), podman-generate(1), podman-play(1) +podman(1), podman-container(1), podman-pod(1), podman-generate-kube(1), podman-play(1) # HISTORY Decemeber 2018, Originally compiled by Brent Baude (bbaude at redhat dot com) |