5 Commits

Include renames

Author	SHA1	Message	Date
claude-botandClaude Opus 5.5	24e969abb0	docs(gpu): the intel-gpu-plugin comment describes its node label ... It still said the DaemonSet has no nodeSelector and runs on every node. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-17 22:15:06 +02:00
claude-botandClaude Opus 5.5	5e115cde11	feat(gpu): iGPU workloads run only where a node declares the iGPU ... llama-server, llama-embed, wiki-embed (gpu.intel.com/i915) and the wiki behind them are bound to the Intel iGPU. On a site without one (Hetzner, restore rehearsal runs 27/28) their pods stayed Pending, and the GPU plugin and exporter DaemonSets sat on every node with nothing to serve. The node patches k8s-1..3 label their machines hardware.renner.uno/intel-gpu=true. The GPU plugin, the exporter, the three llama Deployments and the wiki now select on it. Elsewhere the DaemonSets have no pods and the Deployments stay unscheduled. Production rollout order: the label must be on the nodes (talosctl patch, no reboot) before these manifests reconcile, or the GPU plugin and the llama/wiki pods are removed or left Pending. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-17 22:14:47 +02:00
renovate-bot	68c0978660	chore(deps): update all non-major dependencies	2026-10-05 02:01:26 +00:00
claude-botandClaude Fable 5.1	da8a725b32	feat(intel-gpu-plugin): advertise the monitoring resource ... Enables -enable-monitoring on the device plugin. With 0.36.0 that advertises gpu.intel.com/monitoring, a single resource per node that hands a pod every GPU rather than one of the shared slots; it is what a metrics exporter requests to see the whole iGPU, and it is the only way to get /dev/dri into a pod without a hostPath. Nothing consumes it yet. The nodes currently advertise gpu.intel.com/i915 only — the issue assumed the chart default had this on, but the DaemonSet here is hand-written and did not. Refs #752 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>	2026-09-08 06:51:43 +02:00
claude-botandClaude Opus 5	c868b8cd9d	feat(intel-gpu-plugin): expose the Intel iGPU as gpu.intel.com/i915 ... Adds the Intel GPU device plugin as a DaemonSet in kube-system, making the on-board Iris Xe of each MS-01 node schedulable as `gpu.intel.com/i915`. Pods can then request the iGPU without a /dev/dri hostPath or privilege escalation — the plugin passes the render node through the kubelet device-plugin API. The resource covers QuickSync transcoding as well as GPU compute. Vendored from upstream v0.36.0 rather than installed from the `intel-device-plugins-gpu` Helm chart: that chart renders a `GpuDevicePlugin` custom resource requiring the Intel Device Plugin Operator, its CRDs and a cert-manager webhook. One device type on three identical nodes gives the operator nothing to manage that the DaemonSet does not. Runs in kube-system because the plugin mounts hostPaths; the cluster enforces PodSecurity `baseline`, which forbids those, and kube-system is the only namespace in the API server's exemption list. NFD is not deployed, so upstream's nfd_labeled_nodes overlay and its nodeSelector are omitted. `-shared-dev-num=4` lets several containers share the single iGPU. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-09-01 12:38:42 +02:00