Search Results for "daemon"

Kured (KUbernetes REboot Daemon) is a Kubernetes daemonset that performs safe automatic node reboots when the need to do so is indicated by the package management system of the underlying OS.

kaniko is a tool to build container images from a Dockerfile, inside a container or Kubernetes cluster. kaniko doesn't depend on a Docker daemon and executes each command within a Dockerfile completely in userspace. This enables building container images in environments that can't easily or securely run a Docker daemon, such as a standard Kubernetes cluster.

Virtual Kubelet is an open source Kubernetes kubelet implementation that masquerades as a kubelet for the purposes of connecting Kubernetes to other APIs. This allows the nodes to be backed by other services like ACI, AWS Fargate, IoT Edge, Tensile Kube etc. The primary scenario for VK is enabling the extension of the Kubernetes API into serverless container platforms like ACI and Fargate, though we are open to others. However, it should be noted that VK is explicitly not intended to be an...

cAdvisor (Container Advisor) provides container users an understanding of the resource usage and performance characteristics of their running containers. It is a running daemon that collects, aggregates, processes, and exports information about running containers. Specifically, for each container it keeps resource isolation parameters, historical resource usage, histograms of complete historical resource usage and network statistics. This data is exported by container and machine-wide. cAdvisor has native support for Docker containers and should support just about any other container type out of the box. ...

Fast and flexible Docker image-building tool, that works in unprivileged containerized environments like Mesos and Kubernetes.

lmctfy is Google’s open-source container runtime that exposed Linux cgroups and namespaces through a higher-level API, predating the widespread adoption of modern container tools. It offered a daemon and client for creating, updating, and destroying resource-isolated “containers” with quotas on CPU, memory, and other subsystems. The project focused on operational safety—clean hierarchies, accounting, and predictable behavior under resource pressure—reflecting lessons from running containers at scale. Although it has since been archived in favor of the broader ecosystem, the code remains a reference for how to map kernel primitives to service-oriented container management. ...