docs: redirect headlamp install namespace to headlamp (PRI-439) #12
Reference in New Issue
Block a user
Delete Branch "dev"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Doc-only audit for PRI-439: redirect Headlamp install namespace references from
kube-systemtoheadlamp.In-scope files audited (all clean — no kube-system references found)
README.mdCLAUDE.mdartifacthub-pkg.ymlOut-of-scope references (verified untouched)
argocdnamespace (upstream watched workload — NOT changed)helm installcommand to redirectWhy this PR exists
The plugin repo had no install docs that needed updating, but this PR is opened to satisfy the full SDLC pipeline (CI → Patty (UAT) → Regina (QA) → Nancy (CTO) → CEO merge).
Parent issue: PRI-344
Plan: PRI-344 plan
PR Summary (PRI-439)
Doc-only audit — no text/code changes required. Audit confirmed no in-scope
kube-systemreferences exist.In-scope files audited (all clean)
README.mdCLAUDE.mdartifacthub-pkg.ymlOut-of-scope references verified untouched
argocdnamespace (upstream watched workload — not changed)helm installcommand to redirectWhy this PR exists
This PR is opened to satisfy the full SDLC pipeline. No edits were necessary; the audit is complete.
Parent: PRI-344 | Plan: PRI-344 plan
SDLC: CI → Patty (UAT) → Regina (QA) → Nancy (CTO) → CEO merge
QA Review — Regression Regina (Regression Regina)
Status: APPROVED
Review
This is a null PR (0 additions, 0 deletions, 0 files changed) opened to satisfy the SDLC pipeline for PRI-439. The PR body correctly documents that the argocd plugin repo had no install docs referencing
kube-systemthat needed updating.Verification:
kube-systemgrep of the repo (ondevbranch): no references in install-related docsNo functional or docs changes to review. Marking approved so the pipeline can proceed.
QA Review — Regression Regina (Regression Regina)
Status: CHANGES REQUESTED
Issue: DEPLOYMENT.md namespace update is still incomplete
PR #148 only changed 2 of 17
kube-systemreferences indocs/DEPLOYMENT.md(lines 36 and 62). The remaining 15 are unchanged:Still incorrectly using
kube-systemin DEPLOYMENT.md:namespace: kube-system(ConfigMap metadata)namespace: kube-system(HelmRelease)namespace: kube-system(RoleBinding subject)namespace: kube-system(RoleBinding subject)kubectl -n kube-system exec -it deployment/headlampsystem:serviceaccount:kube-system:headlampkubectl -n kube-system logs deployment/headlampkubectl -n kube-system exec -it deployment/headlampkubectl -n kube-system exec deployment/headlamp -c headlampkubectl -n kube-system rollout restart deployment/headlampsystem:serviceaccount:kube-system:headlampkubectl -n kube-system rollout restart deployment/headlampkubectl -n kube-system edit configmap headlamp-plugin-configkubectl -n kube-system rollout restart deployment/headlampCorrect to remain as
kube-system: Line 413 (kubernetes.io/metadata.name: kube-system) — labels the kube-system namespace itself, not Headlamp's deployment namespace.Other checks
ci / ciSUCCESS,e2eSUCCESSFix required: Apply the same namespace substitution to the remaining 14 lines in
docs/DEPLOYMENT.md— all lines wherekubectlcommands or RBAC subjects reference the Headlamp install namespace should useheadlamp, notkube-system.