Files
Paul Payne 9fd046c378 Bump remaining apps: major version slots and infrastructure
New version slots (major version jumps):
- gitea: 1.24.3 -> 28.2.0 (slot 1 -> 28)
- ghost: 5.130.6 -> 6.72.0 (slot 5 -> 6)
- formbricks: 3.6.0 -> 6.1.0 (slot 3 -> 6)
- mattermost: 10.8.1 -> 12.0.1 (slot 10 -> 12)
- zulip: 9.4 -> 12.3 (slot 9 -> 12)
- immich: 1.135.3 -> 3.3.5 (slot 1 -> 3)
- openproject: 16.1.1 -> 17.9.3 (slot 16 -> 17)
- listmonk: 5.0.3 -> 6.1.0 (slot 5 -> 6)
- discourse: 3.5.3 -> 2026.10.0 (slot 3 -> 2026, calver)

Same-slot large bumps:
- vllm: 0.9.2 -> 0.32.0
- longhorn: v1.8.1 -> v1.13.0

Infrastructure:
- cert-manager: v1.17.2 -> v1.21.2
- coredns: v1.12.0 -> v1.14.7
- externaldns: v0.13.4 -> v0.23.0
- metallb: v0.15.0 -> v0.16.1
- mysql: 9.1.0 -> 9.7.4
- node-feature-discovery: v0.17.3 -> v0.20.1
- nvidia-device-plugin: v0.17.1 -> v0.20.1
2026-10-23 14:18:48 +00:00
..

NVIDIA Device Plugin

The NVIDIA Device Plugin for Kubernetes enables GPU scheduling and resource management on nodes with NVIDIA GPUs.

Overview

This service deploys the official NVIDIA Device Plugin as a DaemonSet that:

  • Discovers NVIDIA GPUs on worker nodes
  • Labels nodes with GPU product information (e.g., nvidia.com/gpu.product=GeForce-RTX-4090)
  • Advertises GPU resources (nvidia.com/gpu) to the Kubernetes scheduler
  • Enables pods to request GPU resources

Prerequisites

Before installing the NVIDIA Device Plugin, ensure that:

  1. NVIDIA Drivers are installed (>= 384.81)
  2. nvidia-container-toolkit is installed (>= 1.7.0)
  3. nvidia-container-runtime is configured as the default container runtime
  4. Worker nodes have NVIDIA GPUs

Talos Linux Requirements

For Talos Linux nodes, you need:

  • NVIDIA drivers extension in the Talos schematic
  • nvidia-container-toolkit extension
  • Proper container runtime configuration

Installation

# Configure and install the service
wild-cluster-services-configure nvidia-device-plugin
wild-cluster-install nvidia-device-plugin

Verification

After installation, verify the plugin is working:

# Check plugin pods are running
kubectl get pods -n kube-system | grep nvidia

# Verify GPU resources are advertised
kubectl get nodes -o json | jq '.items[].status.capacity | select(has("nvidia.com/gpu"))'

# Check GPU node labels
kubectl get nodes --show-labels | grep nvidia

Usage in Applications

Once installed, applications can request GPU resources:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: gpu-app
spec:
  template:
    spec:
      containers:
      - name: app
        image: nvidia/cuda:latest
        resources:
          requests:
            nvidia.com/gpu: 1
          limits:
            nvidia.com/gpu: 1

Troubleshooting

Plugin Not Starting

  • Verify NVIDIA drivers are installed on worker nodes
  • Check that nvidia-container-toolkit is properly configured
  • Ensure worker nodes are not tainted in a way that prevents scheduling

No GPU Resources Advertised

  • Check plugin logs: kubectl logs -n kube-system -l name=nvidia-device-plugin-ds
  • Verify NVIDIA runtime is the default container runtime
  • Ensure GPUs are detected by the driver: check node logs for GPU detection messages

Configuration

The plugin uses the following configuration:

  • Image: nvcr.io/nvidia/k8s-device-plugin:v0.17.1
  • Namespace: kube-system
  • Priority Class: system-node-critical
  • Tolerations: Schedules on nodes with nvidia.com/gpu taint

References