--- # Standalone Valkey (Redis-compatible) for NetBox. The netbox-community chart # bundles a Bitnami Valkey subchart, but we run our own here: it keeps image # control in-estate (valkey/valkey, already allowlisted through the artifactapi # dockerhub mirror), avoids the Bitnami "legacy image" churn, and matches the # standalone-cache pattern used by litellm. One instance serves both NetBox # databases: DB 0 = RQ task queue, DB 1 = cache. AOF persistence is enabled so # queued background jobs survive a restart. apiVersion: apps/v1 kind: Deployment metadata: name: netbox-valkey namespace: netbox labels: app.kubernetes.io/name: netbox app.kubernetes.io/component: valkey spec: replicas: 1 selector: matchLabels: app: netbox-valkey strategy: type: Recreate template: metadata: labels: app: netbox-valkey app.kubernetes.io/name: netbox app.kubernetes.io/component: valkey spec: securityContext: fsGroup: 999 containers: - name: valkey image: valkey/valkey:8-alpine imagePullPolicy: IfNotPresent command: - valkey-server - --appendonly - "yes" - --save - "60" - "1" ports: - containerPort: 6379 name: valkey protocol: TCP securityContext: allowPrivilegeEscalation: false runAsNonRoot: true runAsUser: 999 capabilities: drop: - ALL livenessProbe: exec: command: - valkey-cli - ping failureThreshold: 3 initialDelaySeconds: 30 periodSeconds: 30 successThreshold: 1 timeoutSeconds: 5 readinessProbe: exec: command: - valkey-cli - ping failureThreshold: 3 initialDelaySeconds: 5 periodSeconds: 10 successThreshold: 1 timeoutSeconds: 5 resources: limits: cpu: 500m memory: 512Mi requests: cpu: 50m memory: 128Mi volumeMounts: - mountPath: /data name: data restartPolicy: Always volumes: - name: data persistentVolumeClaim: claimName: netbox-valkey-data