opensource/podman
1
0
Fork 0
mirror of https://github.com/containers/podman.git synced 2025-06-24 03:08:13 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #2438 from vrothberg/scope-v2

Browse Source 
[skip ci] readme/docs update
This commit is contained in:
OpenShift Merge Robot
2019-02-26 15:27:11 +01:00
committed by GitHub
parent 02988f17f6 7fea0d7077
commit 8a5e103876
3 changed files with 13 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@ -36,10 +36,14 @@ This project tests all builds against each supported version of Fedora, the late
* Container runtimes daemons for working with the Kubernetes CRI interface.
[CRI-O](https://github.com/kubernetes-sigs/cri-o) specializes in that.
* Supporting `docker-compose`. We believe that Kubernetes is the defacto
standard for container orchestration. Hence, Podman allows the creation of
Pods from a Kubernetes YAML file. See
[podman-play-kube](https://github.com/containers/libpod/blob/master/docs/podman-play-kube.1.md)
for more details.
standard for composing Pods and for orchestrating containers, making
Kubernetes YAML a defacto standard file format. Hence, Podman allows the
creation and execution of Pods from a Kubernetes YAML file (see
[podman-play-kube](https://github.com/containers/libpod/blob/master/docs/podman-play-kube.1.md)).
Podman can also generate Kubernetes YAML based on a container or Pod (see
[podman-generate-kube](https://github.com/containers/libpod/blob/master/docs/podman-generate-kube.1.md)),
which allows for an easy transition from a local development environment
to a production Kubernetes cluster.
## OCI Projects Plans

4
docs/podman-generate-kube.1.md
View File

@ -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)

4
docs/podman-play-kube.1.md
View File

@ -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)