Difference between revisions of "Container Runtime Interface (CRI)"
Jump to navigation
Jump to search
| Line 18: | Line 18: | ||
== See also == | == See also == | ||
| + | * {{crictl}} | ||
| + | * {{kubelet}} | ||
* {{CRI}} | * {{CRI}} | ||
* {{containers}} | * {{containers}} | ||
[[Category:Kubernetes]] | [[Category:Kubernetes]] | ||
Revision as of 04:55, 23 September 2022
- https://kubernetes.io/docs/concepts/architecture/cri/
- https://kubernetes.io/blog/2016/12/container-runtime-interface-cri-in-kubernetes/
kubelet communicates with the container runtime (or a CRI shim for the runtime) over Unix sockets using the gRPC framework, where kubelet acts as a client and the CRI shim as the server.
News
- 05/2022 Kubernetes 1.24:
dockershimremoved fromkubelet
Related
See also
crictl [ logs | ps | pods | exec | config | images ], /etc/crictl.yaml, crictl --help, Kubelet Container Runtime Interface (CRI)kubelet, Pod Lifecycle Event Generator (PLEG), Kubelet conditions,/etc/kubernetes/kubelet.conf, /var/log/kubelet.log, Kubelet Container Runtime Interface (CRI),crictl,context deadline exceeded, E1122, E1124, Starting kubelet, NodeHasDiskPressure, NodeHasInsufficientMemory, rebooted, Node-pressure Eviction, Kubelet logs,manager: kubelet- Open Container Initiative (OCI), CRI, CRI-O,
crictl, cri-dockerd - Containers, OCI: Docker (
dockerd),containerd,runc, Podman, buildah, skopeo, lxd, Container Registry, Service mesh, Windows Server containers, Containerpilot, CoreOS, CAdvisor, Containers networking, Container scanning, cosign, CRI, CRI-O,initContainers, Sidecar container, Container images, latest
Advertising:
