Container Runtime Interface client implementation
This repository contains the client source code for the Container Runtime Interface (CRI). CRI is a plugin interface which enables 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 at kubernetes docs.
The repository kubernetes/cri-client is a mirror of https://github.com/kubernetes/kubernetes/tree/master/staging/src/k8s.io/cri-client. Please do not file issues or submit PRs against the kubernetes/cri-client repository as it is readonly, all development is done in kubernetes/kubernetes.
The cri-api staging repository is
defined in kubernetes/kubernetes
and is only intended to be used for kubelet to container runtime
interactions, or for node-level troubleshooting using a tool such as crictl.
The cri-api wraps the Protobuf protocol definition
with extra features which can be used directly from other clients as well.
It is not a common purpose container runtime API for general use, and is
intended to be Kubernetes-centric. We try to avoid it, but there may be logic
within a container runtime that optimizes for the order or specific parameters
of call(s) that the kubelet makes.
Learn how to engage with the Kubernetes community on the community page.
You can reach the maintainers of this repository at:
- Slack: #sig-node (on https://kubernetes.slack.com -- get an invite at slack.kubernetes.io)
- Mailing List: https://groups.google.com/forum/#!forum/kubernetes-sig-node
Participation in the Kubernetes community is governed by the Kubernetes Code of Conduct.
See CONTRIBUTING.md for more information. Please note that kubernetes/cri-api is a readonly mirror repository, all development is done at kubernetes/kubernetes.