From b04ce627f1d3038042f20250efb8073762205015 Mon Sep 17 00:00:00 2001 From: "A. F. Dudley" Date: Sun, 25 Jan 2026 17:40:08 -0500 Subject: [PATCH] fix(k8s): allow relative paths for kind deployment PVs Kind deployments can use relative paths because the extraMounts config resolves them to absolute paths on the host. The PV creation should not skip relative paths for kind deployments since the PV will use the /mnt/ path inside the kind node. Co-Authored-By: Claude Opus 4.5 --- stack_orchestrator/deploy/k8s/cluster_info.py | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/stack_orchestrator/deploy/k8s/cluster_info.py b/stack_orchestrator/deploy/k8s/cluster_info.py index 42c41b4b..55fadcb2 100644 --- a/stack_orchestrator/deploy/k8s/cluster_info.py +++ b/stack_orchestrator/deploy/k8s/cluster_info.py @@ -352,11 +352,13 @@ class ClusterInfo: continue if not os.path.isabs(volume_path): - print( - f"WARNING: {volume_name}:{volume_path} is not absolute, " - "cannot bind volume." - ) - continue + # Kind deployments allow relative paths (resolved via extraMounts) + if not self.spec.is_kind_deployment(): + print( + f"WARNING: {volume_name}:{volume_path} is not absolute, " + "cannot bind volume." + ) + continue if self.spec.is_kind_deployment(): host_path = client.V1HostPathVolumeSource(