kubernetes/cri-api

Container Runtime Interface (CRI) – a plugin interface which enables kubelet to use a wide variety of container runtimes.

Kubernetes (K8s)

---

Kubernetes, also known as K8s, is an open source system for managing containerized applications across multiple hosts. It provides basic mechanisms for the deployment, maintenance, and scaling of applications.

Kubernetes builds upon a decade and a half of experience at Google running production workloads at scale using a system called Borg, combined with best-of-breed ideas and practices from the community.

Kubernetes is hosted by the Cloud Native Computing Foundation (CNCF). If your company wants to help shape the evolution of technologies that are container-packaged, dynamically scheduled, and microservices-oriented, consider joining the CNCF. For details about who's involved and how Kubernetes plays a role, read the CNCF announcement.

---

To start using K8s

See our documentation on kubernetes.io.

Take a free course on Scalable Microservices with Kubernetes.

To use Kubernetes code as a library in other applications, see the list of published components. Use of the k8s.io/kubernetes module or k8s.io/kubernetes/... packages as libraries is not supported.

To start developing K8s

The community repository hosts all information about building Kubernetes from source, how to contribute code and documentation, who to contact about what, etc.

If you want to build Kubernetes right away there are two options:

You have a working Go environment.

git clone https://github.com/kubernetes/kubernetes
cd kubernetes
make

You have a working Docker environment.

git clone https://github.com/kubernetes/kubernetes
cd kubernetes
make quick-release

For the full story, head over to the developer's documentation.

Support

If you need support, start with the troubleshooting guide, and work your way through the process that we've outlined.

That said, if you have questions, reach out to us one way or another.

Community Meetings

The Calendar has the list of all the meetings in the Kubernetes community in a single location.

Adopters

The User Case Studies website has real-world use cases of organizations across industries that are deploying/migrating to Kubernetes.

Governance

Kubernetes project is governed by a framework of principles, values, policies and processes to help our community and constituents towards our shared goals.

The Kubernetes Community is the launching point for learning about how we organize ourselves.

The Kubernetes Steering community repo is used by the Kubernetes Steering Committee, which oversees governance of the Kubernetes project.

Roadmap

The Kubernetes Enhancements repo provides information about Kubernetes releases, as well as feature tracking and backlogs.

cri-api's Issues

Move off of `gogo/protobuf`

The gogo/protobuf library is deprecated: https://github.com/gogo/protobuf

And it would be advantageous for cri-api to consider moving away from gogo/protobuf in order to de-risk using this library. Previous high severity CVEs have appeared in the past for this library: GHSA-c3h9-896r-86jm

And other Go modules in the community have moved away from it (like containerd here: containerd/containerd#6564

Add support for getting CMD and ENTRYPOINT for containers

Hi Team,
We are looking for getting CMD and ENTRYPOINT details for containers. Also we are looking for API support for Image Inspect ?

Could you please help us, how to get these details ?

Thanks,
Sunil

cri stats test doesn't specify cgroup

cri support support pause

cri support container pause

Add support to image labels

Currently the Type Image doesn't provide label information associated with the image at creation time, for example in a Dockerfile it is possible to add labels by using:

LABEL "com.mydomain.image.distro.id"="${DISTRO_ID}" \
      "com.mydomain.image.distro.codename"="${DISTRO_CODENAME}" \
      "com.mydomain.image.distro.release"="${DISTRO_RELEASE}" \
      "com.mydomain.image.distro.build_id"="${BUILD_ID}"

Would be possible to improve this in future?
I'm working on an image stats collector, for internal reports, and I was looking to retrieve this info in a general way instead of having two clients, one for docker and another for containerd.

Volume instances

We now have a working csi driver (located here: https://github.com/kubernetes-csi/csi-driver-image-populator) that lets you use a container image as a volume.

The current implementation uses buildah to download the image, create a new, non running container, and then mount it.

This is particular to the layout of the buildah/crio toolchain though.

I'd like to propose an api be added to cri to allow creating an instance for the purposes of using it as a volume. The csi-driver-image-populator could then speak to the chosen cri backend to provision the volume instances rather then doing it itself.

wrong

Create a SECURITY_CONTACTS file.

As per the email sent to kubernetes-dev[1], please create a SECURITY_CONTACTS
file.

The template for the file can be found in the kubernetes-template repository[2].
A description for the file is in the steering-committee docs[3], you might need
to search that page for "Security Contacts".

Please feel free to ping me on the PR when you make it, otherwise I will see when
you close this issue. :)

Thanks so much, let me know if you have any questions.

(This issue was generated from a tool, apologies for any weirdness.)

[1] https://groups.google.com/forum/#!topic/kubernetes-dev/codeiIoQ6QE
[2] https://github.com/kubernetes/kubernetes-template-project/blob/master/SECURITY_CONTACTS
[3] https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance-template-short.md

How to get the specific container ContainerConfig by cri-api ?

Hi team,

I'm working on some tools which need to be interacting with cri-api, but I found that it's hard to get the ContainerConfig of a running container:

criapi, err := remote.NewRemoteRuntimeService("/run/containerd/containerd.sock", containerd.WithTimeout(10 * time.Second))
if err != nil {
     panic(err)
}
cid = "<A_CONTAINER_ID>"
containerStatus, err := criapi.ContainerStatus(cid)
if err != nil {
     panic(err)
}
// But there is no container config data, e.g. container envs.

So we did have a ContainerConfig while doing CreateContainer, how do we get such config data for running containers?

Thanks!

Uploading the CRI Socket information ends up with error uploading crisocket!

So, first things first!

For the last couple of weeks we have tried to pin point what is going on and what is not working. Everytime we ends up with both patchnode.go:30] [patchnode] Uploading the CRI Socket information "/var/run/dockershim.sock" to the Node API object "DELTED_INFO" as an annotation [kubelet-check] Initial timeout of 40s passed. timed out waiting for the condition error uploading crisocket

The setup is running on Debain 10, with Docker and Kubernetes + Flannel as the CNI. All ports that is necessary for it to work is open, and we even allowed all traffic between the cluster, but everytime we ends up with the crisocket time out as above.

Today I did a reset on master + slaves, replaced the Flannel CNI with Calico and all went well!

The only thing I did was to replace the Flannel with Calico, everything else is untouched. So it looks like there is a problem with the CRI plugin and the Flannel CNI, but I can't put a finger on it what is not working.

stdout/stderr conflicts with stdio.h

We are using protobuf 3.13.0 to compile cri api.

In api.proto:

message ExecSyncResponse {
    // Captured command stdout output.
    bytes stdout = 1;
    // Captured command stderr output.
    bytes stderr = 2;
    // Exit code the command finished with. Default: 0 (success).
    int32 exit_code = 3;
}

The <stdio.h> has macros:

#define stdin  (stdin)
#define stdout (stdout)
#define stderr (stderr)

Errors:

stdio.h:65:16: note: expanded from macro 'stdout'
#define stdout (stdout)
^
cri/src/api.pb.cc:28327:13: error: expected unqualified-id

CRI should expose a "Container l/c

watch container start or stop

cri-api does not seem to have an interface to view container start and stop events