diff options
author | OpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com> | 2020-02-13 16:00:51 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-02-13 16:00:51 +0100 |
commit | e4e5efc12b7902a22561170ca59f3da90b7b80ce (patch) | |
tree | 6681d529a41b869f34e90da7863611c495093b3f | |
parent | cd9e6b4143c9b49c3a23f2ba3c1e1c4978c83134 (diff) | |
parent | f8443eb83af941efbfbb2b302c013e8235d13ef4 (diff) | |
download | podman-e4e5efc12b7902a22561170ca59f3da90b7b80ce.tar.gz podman-e4e5efc12b7902a22561170ca59f3da90b7b80ce.tar.bz2 podman-e4e5efc12b7902a22561170ca59f3da90b7b80ce.zip |
Merge pull request #5195 from vrothberg/fix-5106
[CI:DOCS] README: fix docs links
-rw-r--r-- | README.md | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -73,9 +73,9 @@ A little configuration by an administrator is required before rootless Podman ca 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-play-kube](https://github.com/containers/libpod/blob/master/docs/source/markdown/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)), + [podman-generate-kube](https://github.com/containers/libpod/blob/master/docs/source/markdown/podman-generate-kube.1.md)), which allows for an easy transition from a local development environment to a production Kubernetes cluster. If Kubernetes does not fit your requirements, there are other third-party tools that support the docker-compose format such as |