Synthèse
HAMi is composed of several components: Mutating Webhook: Intercepts pod submissions in the Kubernetes API server and rewrites scheduler fields and resource requests for workloads requesting virtualized devices. Scheduler Extender: Filters, scores, and binds pods to nodes and devices using binpack, spread, and topology-aware placement policies. Device Plugins: Vendor-specific plugins that register accelerators with Kubernetes and allocate fractional device resources to containers. HAMi-
HAMi is composed of several components: Mutating Webhook: Intercepts pod submissions in the Kubernetes API server and rewrites scheduler fields and resource requests for workloads requesting virtualized devices. Scheduler Extender: Filters, scores, and binds pods to nodes and devices using binpack, spread, and topology-aware placement policies. Device Plugins: Vendor-specific plugins that register accelerators with Kubernetes and allocate fractional device resources to containers. HAMi-Core: The in-container virtualization layer that enforces hard runtime limits on GPU memory and compute, intercepting the native CUDA driver for NVIDIA devices. HAMi-WebUI: A visual interface for cluster and device management, giving operators visibility into allocation and utilization across the fleet.
Observability Layer: A Prometheus-compatible metrics endpoint and Grafana dashboard examples for monitoring accelerator usage cluster-wide.
Source originale
cncf.io
CORTEX