Search Results for "test"

CLI and validation tools for Kubelet Container Runtime Interface (CRI). cri-tools aims to provide a series of debugging and validation tools for Kubelet CRI. It's recommended to use the same cri-tools and Kubernetes minor version, because new features added to the Container Runtime Interface (CRI) may not be fully supported if they diverge. cri-tools follows the Kubernetes release cycles with respect to its minor versions (1.x.y). Patch releases (1.x.z) for Kubernetes are not in sync with...

An open framework to assemble specialized container systems without reinventing the wheel. Moby is an open framework created by Docker to assemble specialized container systems without reinventing the wheel. It provides a “lego set” of dozens of standard components and a framework for assembling them into custom platforms. At the core of Moby is a framework to assemble specialized container systems which provides a library of containerized components for all vital aspects of a container...

...By creating a custom resource (a KuberhealthyCheck) in your cluster, you can easily enable various synthetic tests and get Prometheus metrics for them. Kuberhealthy comes with lots of useful checks already available to ensure the core functionality of Kubernetes, but checks can be used to test anything you like. We encourage you to write your own check container in any language to test your own applications. It really is quick and easy.

NAML is a Go library and command line tool that can be used as a framework to develop and deploy Kubernetes applications. Kubernetes applications are complicated, so let's use a proper Turing complete language to reason about them.

...The system speaks registry protocols and understands layered image formats, resolving whiteouts and overlays so the mounted view matches what a container runtime would see. A FUSE (or platform-equivalent) frontend makes it trivial to integrate with existing tools: compilers, test runners, or debuggers can read files as if they were local. This lazy, verified access pattern is especially valuable in CI and developer workflows where you inspect or compile a few files from a massive base image. By treating registries as a read-only filesystem, CRFS turns image artifacts into first-class, quickly accessible build inputs.