Proto commits in containerd/nri

These 15 commits are when the Protocol Buffers files have changed:

2025-03-04

api: add more data for container status. Add exit code, status reason and message, and timestamps for creation, start and exit to container data. Co-authored-by: Mike Brown <brownwm@us.ibm.com> Signed-off-by: Krisztian Litkey <krisztian.litkey@intel.com>

The documentation is generated from this commit.

2025-02-28

api,adaptation,generate: allow setting container command line. Allow setting (or updating already set) container command line arguments. Signed-off-by: Krisztian Litkey <krisztian.litkey@intel.com>

2025-02-13

Add UpdatePodSandbox to NRI plugin API This API is called by the container runtime to update pod sandbox resources when they change. This is for the In-place Pod Resize KEP-1287. Signed-off-by: Chris Henzie <chrishenzie@google.com>

2024-12-06

Add WASM plugin support Signed-off-by: Sascha Grunert <sgrunert@redhat.com>

2024-10-26

api: support Pod IPs Allow NRI plugins to read the allocated IPs to the pod on the PodSandbox hooks. This is specially useful for networking daemons that depend on the Pod IPs assigned via CNI by the container runtime (service mesh, network policies, ... ) to create seamless integrations without having to modify the existing environment. Existing network integrations use techniques like: - CNI chaining (invasive) as the implementation needs to modify the existing deployment and can cause disruption due to mutations on the existing configurations. - Read Pod Status, that is too late in the process, since the pod lifecycle does not update the pod status until the containers are running, but there are applications like network policy implemetnations or service meshes that needs this information before the pod is completely created. - Inspect the host namespaces to gather the information, that is very intrusive and not portable, creating a tighly coupling between. Add a nri plugin that can be used as reference implementations for this integration, the nri plugin just log the interesting networking details of the pod (ips and network namespace) on the different hooks of the pod lifecucle. Change-Id: Idb9605c719903d0df51c9a1947e0f838870b5c0b Signed-off-by: Antonio Ojea <aojea@google.com>

2024-10-10

api: add support for multiple sync messages. Signed-off-by: Krisztian Litkey <krisztian.litkey@intel.com>

2024-09-27

api,adaptation,stub: let plugin know configured timeouts. Let plugins know the configured registration and request processing timeout. Signed-off-by: Krisztian Litkey <krisztian.litkey@intel.com>

2024-08-27

pkg,plugins,.codespellrc: add codespellrc, fix spelling. Add .codespellrc, fix reported existing spelling errors. Signed-off-by: Krisztian Litkey <krisztian.litkey@intel.com>

2024-08-19

NRI plugins support adjust oom_score_adj Signed-off-by: Xiaojin Zhang <874478410@qq.com>

2024-08-12

api: add support for native CDI device injection. Add support for native CDI injection. With this in place, a plugin can now directly request injection of CDI devices by device name. This is much simpler than first performing CDI device resolution and injection, followed by a set of low- level NRI adjustments for devices, mounts, env. vars. and OCI hooks to effectively do the same. Signed-off-by: Krisztian Litkey <krisztian.litkey@intel.com>

2024-07-19

support pids cgroup Signed-off-by: Yang Yang <yang8518296@163.com>

2023-08-19

api: add POSIXRlimit type Signed-off-by: Samuel Karp <samuelkarp@google.com>

2022-11-11

pkg/api: define updated NRI plugin API. Define a ttRPC-based updated NRI API which allows plugins more flexible control over containers with less overhead per plugin invocation/request. The new protocol allows plugins to - synchronize their state with the runtime on startup - subscribe for pod and container lifecycle events - adjust a subset of container parameters at creation - update assigned container resources otherwise The API allows adjusting the following parameters during container creation: - annotations - environment variables - mounts, devices - OCI hooks - assigned cgroupfs-controlled resources, including o scheduling parameters o memory and huge page limits o CPU and memory pinning o unified cgroup v2 parameters o RDT class (LLC, memory BW control) o Block I/O class (blkio controller parameters) The API allows updating the following container parameters otherwise: - assigned cgroupfs-controlled resources Signed-off-by: Krisztian Litkey <krisztian.litkey@intel.com>

2021-03-16

remove vendor directory This project is used as a library and doesn't produce binaries, in which case convention is to not use vendoring. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

This commit does not contain any .proto files.

2020-07-29

Vendor go modules Signed-off-by: Michael Crosby <michael@thepasture.io>