CRI API version skew policy

Mon, 01 Jan 0001 00:00:00 +0000

CRI is a plugin interface which enables the kubelet to use a wide variety of container runtimes, without the need to recompile. CRI consists of a protocol buffers and gRPC API. Read more about CRI API at kubernetes docs .

The CRI API is only intended to be used for the kubelet to container runtime interactions, or for node-level troubleshooting using a tool such as crictl. It is not a common purpose container runtime API for general use, and is intended to be Kubernetes-centric. This is why there may be an undocumented logic within a container runtimes that assumes the order or specific parameters of call(s) that the kubelet makes. Attempts to call CRI API in a different order by a client different than the kubelet, might result in unrecoverable error. Whenever discovered, this logic is being documented and avoided.

Kubernetes feature development and container runtimes

Mon, 01 Jan 0001 00:00:00 +0000

The mechanics of a feature development that requires new CRI APIs is covered in documentation on CRI API feature-development . This article defines policies for developing new Kubernetes features that require CRI API changes. The goal of these policies is to ensure great user experience for people trying the new feature early, adopting it when it is enabled by default, and relying on it as a GA functionality.

Code Organization on Kubernetes Contributors

CRI API version skew policy

Kubernetes feature development and container runtimes