From b9148c805198d5cc911da096b45aa8968b1a0fcb Mon Sep 17 00:00:00 2001 From: Prathamesh Musale Date: Mon, 20 Apr 2026 13:41:58 +0000 Subject: [PATCH] docs(k8s): note namespace naming constraints in the ownership error Tell the user the valid namespace-name shape so they don't pick a suffix that k8s will reject (uppercase, underscores, etc.). Co-Authored-By: Claude Opus 4.7 (1M context) --- stack_orchestrator/deploy/k8s/deploy_k8s.py | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/stack_orchestrator/deploy/k8s/deploy_k8s.py b/stack_orchestrator/deploy/k8s/deploy_k8s.py index 53c48ef8..87f79257 100644 --- a/stack_orchestrator/deploy/k8s/deploy_k8s.py +++ b/stack_orchestrator/deploy/k8s/deploy_k8s.py @@ -231,7 +231,10 @@ class K8sDeployer(Deployer): "\nFix: add an explicit `namespace:` override to this " "deployment's spec.yml so it lands in its own " "namespace. For example:\n" - f" namespace: {self.k8s_namespace}-" + f" namespace: {self.k8s_namespace}-\n" + "\n(k8s namespace names must be lowercase alphanumeric " + "plus '-', start and end with an alphanumeric character, " + "≤63 chars.)" ) if not owner: # Legacy namespace (pre-dates this check) or user-created.