vbatts/cri-o
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
cri-o/cmd/kpod
History
umohnani8 f9b9f92d3f Remove repeated app.Flags in cmd/kpod/main.go 
Signed-off-by: umohnani8 <umohnani@redhat.com>
2017-07-12 11:59:45 -04:00
..
common.go Add 'kpod images' and 'kpod rmi' commands 2017-07-11 15:52:57 -04:00
common_test.go Add 'kpod images' and 'kpod rmi' commands 2017-07-11 15:52:57 -04:00
images.go Add 'kpod images' and 'kpod rmi' commands 2017-07-11 15:52:57 -04:00
images_test.go Add 'kpod images' and 'kpod rmi' commands 2017-07-11 15:52:57 -04:00
launch.go Add basic skeleton of kpod executable 2016-12-01 22:42:54 -05:00
main.go Remove repeated app.Flags in cmd/kpod/main.go 2017-07-12 11:59:45 -04:00
pull.go Add 'kpod pull' command 2017-07-11 09:05:17 -04:00
README.md Rename ocid to crio. 2017-05-12 09:56:06 -04:00
rmi.go Add 'kpod images' and 'kpod rmi' commands 2017-07-11 15:52:57 -04:00
rmi_test.go Add 'kpod images' and 'kpod rmi' commands 2017-07-11 15:52:57 -04:00
tag.go Add kpod tag command 2017-07-06 10:10:51 -04:00
version.go kpod: version should not fail 2017-07-10 17:02:13 -04:00

README.md

kpod - Simple debugging tool for pods and images

kpod is a simple client only tool to help with debugging issues when daemons such as CRI runtime and the kubelet are not responding or failing. A shared API layer could be created to share code between the daemon and kpod. kpod does not require any daemon running. kpod utilizes the same underlying components that crio uses i.e. containers/image, container/storage, oci-runtime-tool/generate, runc or any other OCI compatible runtime. kpod shares state with crio and so has the capability to debug pods/images created by crio.

Use cases

  1. List pods.
  2. Launch simple pods (that require no daemon support).
  3. Exec commands in a container in a pod.
  4. Launch additional containers in a pod.
  5. List images.
  6. Remove images not in use.
  7. Pull images.
  8. Check image size.
  9. Report pod disk resource usage.