Difference between revisions of "Container Runtime Interface (CRI)"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | https://kubernetes.io/docs/concepts/architecture/cri/ | + | * https://kubernetes.io/docs/concepts/architecture/cri/ |
| + | * https://kubernetes.io/blog/2016/12/container-runtime-interface-cri-in-kubernetes/ | ||
| + | |||
| + | <code>[[kubelet]]</code> 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. | ||
| + | https://f.v1.n0.cdn.getcloudapp.com/items/0I3X2U0S0W3r1D1z2O0Q/Image%202016-12-19%20at%2017.13.16.png | ||
| + | |||
== News == | == News == | ||
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
- 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:
