vbatts/cri-o
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
cri-o/cmd/kpod
History
Ryan Cole 2cb57e0cb5 Switch kpod save to use config 
Signed-off-by: Ryan Cole <rcyoalne@gmail.com>
2017-07-28 15:51:11 -04:00
..
docker Implement kpod inspect 2017-07-21 08:11:27 -04:00
common.go Update kpod commands to use getConfig() 2017-07-27 15:58:55 -04:00
common_test.go move image-related functions out of cmd/kpod/common.go and into libkpod/image 2017-07-24 14:34:55 -04:00
history.go Update kpod commands to use getConfig() 2017-07-27 15:58:55 -04:00
images.go Merge pull request #693 from 14rcole/libkpod-config 2017-07-28 06:24:45 -07:00
info.go Update kpod commands to use getConfig() 2017-07-27 15:58:55 -04:00
inspect.go Update kpod commands to use getConfig() 2017-07-27 15:58:55 -04:00
main.go Merge pull request #678 from umohnani8/kpod_save 2017-07-28 10:49:49 -07:00
pull.go Update kpod commands to use getConfig() 2017-07-27 15:58:55 -04:00
push.go Update kpod commands to use getConfig() 2017-07-27 15:58:55 -04:00
README.md Rename ocid to crio. 2017-05-12 09:56:06 -04:00
rmi.go Update kpod commands to use getConfig() 2017-07-27 15:58:55 -04:00
save.go Switch kpod save to use config 2017-07-28 15:51:11 -04:00
tag.go Update kpod commands to use getConfig() 2017-07-27 15:58:55 -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.