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>
This commit is contained in:
parent
2ce8a1c890
commit
7fea0d7077
|
|
@ -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)
|
||||
|
|
|
|||
|
|
@ -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)
|
||||
|
|
|
|||
Loading…
Reference in New Issue