Difference between revisions of "Container Runtime Interface (CRI)"
Jump to navigation
Jump to search
| Line 20: | Line 20: | ||
== See also == | == See also == | ||
* {{crictl}} | * {{crictl}} | ||
| − | |||
* {{CRI}} | * {{CRI}} | ||
* {{containers}} | * {{containers}} | ||
[[Category:Kubernetes]] | [[Category:Kubernetes]] | ||
Latest revision as of 09:34, 28 September 2023
- 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[edit]
- 05/2022 Kubernetes 1.24:
dockershimremoved fromkubelet
Related[edit]
- Container runtime
- CRI-O (OCI)
cri-dockerdcrictldockershimkubectl dds- Kubernetes controller manager
See also[edit]
crictl [ logs | ps | pods | exec | config | images ], /etc/crictl.yaml, crictl --help, Kubelet Container Runtime Interface (CRI)- 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:
