mirror of
https://github.com/containers/podman.git
synced 2025-08-06 11:32:07 +08:00
README: refine "Out of scope" section
Based on user feedback, refine the "Out of scope" section regarding `docker-compose`: * Explain why Podman uses Kubernetes YAML. * Explain how `podman-play-kube` and `podman-generate-kube` fit into the picture. Addresses: https://github.com/containers/libpod/pull/2428#discussion_r259996507 Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
This commit is contained in:
12
README.md
12
README.md
@ -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
|
||||
|
||||
|
Reference in New Issue
Block a user