From 8b88e1376296a7a577f8240bbd1ce0403b0bc57c Mon Sep 17 00:00:00 2001
From: Story Crater Bot <19826264+Riotpiaole@users.noreply.github.com>
Date: Tue, 11 Aug 2026 16:12:13 -0700
Subject: [PATCH] fix(portainer): pin to az-b (talos-cp-2), the real Longhorn
 storage node

nodeSelector still targeted az-a/talos-cp-1 from before the 3-CP topology
change. talos-cp-2 (az-b) has the dedicated Longhorn disks now, so the
pod's zone pin and the PVC's only viable replica location never matched
- ReplicaSchedulingFailure: disks are unavailable, pod stuck
ContainerCreating waiting on AttachVolume.
---
 k8s/apps/portainer/portainer-values.yaml | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/k8s/apps/portainer/portainer-values.yaml b/k8s/apps/portainer/portainer-values.yaml
index b323258..5d97068 100644
--- a/k8s/apps/portainer/portainer-values.yaml
+++ b/k8s/apps/portainer/portainer-values.yaml
@@ -52,7 +52,8 @@ tolerations:
     operator: Exists
     effect: NoSchedule
 
-# Pin to az-a (talos-cp-1) — sole Longhorn storage node. Its RWO PVC can only
-# attach there; without this the pod may land on cp-2/cp-3 and fail to mount.
+# Pin to az-b (talos-cp-2) — sole Longhorn storage node (dedicated disks).
+# Its RWO PVC can only attach there; without this the pod may land on
+# cp-1/cp-3 and fail to mount.
 nodeSelector:
-  topology.kubernetes.io/zone: az-a
+  topology.kubernetes.io/zone: az-b