diff options
Diffstat (limited to 'transfer.md')
| -rw-r--r-- | transfer.md | 20 |
1 files changed, 9 insertions, 11 deletions
diff --git a/transfer.md b/transfer.md index 95fd7a2e7..3f188cf84 100644 --- a/transfer.md +++ b/transfer.md @@ -1,12 +1,12 @@ -# CRI-O Usage Transfer +# KPOD Usage Transfer -This document outlines useful information for ops and dev transfer as it relates to infrastructure that utilizes CRI-O. +This document outlines useful information for ops and dev transfer as it relates to infrastructure that utilizes KPOD. ## Operational Transfer ## Abstract -The `crio` daemon is intended to provide the [CRI](https://github.com/kubernetes/community/blob/master/contributors/devel/container-runtime-interface.md) socket needed for Kubernetes to use for automating deployment, scaling, and management of containerized applications (See the document for [configuring kubernetes to use CRI-O](./kubernetes.md) for more information on that). +The `crio` daemon is intended to provide the [CRI](https://github.com/kubernetes/community/blob/master/contributors/devel/container-runtime-interface.md) socket needed for Kubernetes to use for automating deployment, scaling, and management of containerized applications (See the document for [configuring kubernetes to use KPOD](./kubernetes.md) for more information on that). Therefore the `crioctl` command line is a client that interfaces to the same grpc socket as the kubernetes daemon would, for talking to the `crio` daemon. In many ways `crioctl` is only as feature rich as the Kubernetes CRI requires. There are additional tools e.g. `kpod` and [`buildah`](https://github.com/projectatomic/buildah) that provide a feature rich set of commands for all operational needs in a Kubernetes environment. @@ -20,24 +20,22 @@ As well as some systemd helpers like `systemd-cgls` and `systemd-cgtop` are stil ## Equivalents For many troubleshooting and information collection steps, there may be an existing pattern. -Following provides equivalent with CRI-O tools for gathering information or jumping into containers, for operational use. +Following provides equivalent with KPOD tools for gathering information or jumping into containers, for operational use. -| Existing Step | CRI-O (and friends) | +| Existing Step | KPOD (and friends) | | :---: | :---: | -| `docker exec` | [`crioctl ctr exec`](./docs/crio.8.md) | +| `docker exec` | [`kpod exec`](./docs/kpod-exec.1.md) | | `docker info` | [`kpod info`](./docs/kpod-info.1.md) | | `docker inspect` | [`kpod inspect`](./docs/kpod-inspect.1.md) | | `docker logs` | [`kpod logs`](./docs/kpod-logs.1.md) | -| `docker ps` | [`crioctl ctr list`](./docs/crio.8.md) or [`runc list`](https://github.com/opencontainers/runc/blob/master/man/runc-list.8.md) | -| `docker stats` | [`kpod stats`](./docs/kpod-stats.1.md) or `crioctl ctr status`| - -If you were already using steps like `kubectl exec` (or `oc exec` on OpenShift), they will continue to function the same way. +| `docker ps` | [`kpod ps`](./docs/kpod-ps.1.md) | +| `docker stats` | [`kpod stats`](./docs/kpod-stats.1.md)| ## Development Transfer There are other equivalents for these tools -| Existing Step | CRI-O (and friends) | +| Existing Step | KPOD (and friends) | | :---: | :---: | | `docker attach` | [`kpod exec`](./docs/kpod-attach.1.md) ***| | `docker build` | [`buildah bud`](https://github.com/projectatomic/buildah/blob/master/docs/buildah-bud.md) | |