fix: revert docs namespace to kube-system and use KUBE_VIP_NAMESPACE constant

Revert namespace references from headlamp back to kube-system in docs since kube-vip workload runs in kube-system namespace (not headlamp which is the Headlamp plugin install namespace). Changes: - CLAUDE.md: revert data sources and key constants namespace - README.md: revert requirements line and troubleshooting table - SECURITY.md: revert plugin scope namespaces - OverviewPage.tsx: use KUBE_VIP_NAMESPACE constant instead of hardcoded string Fixes PRI-562
chore: retrigger CI after base branch fix
2026-05-04 20:27:09 +00:00 · 2026-05-04 18:50:35 +00:00 · 2026-05-04 18:49:46 +00:00 · 2026-05-04 16:25:02 +00:00 · 2026-05-04 07:51:05 +00:00
3 changed files with 19856 additions and 2 deletions
@@ -66,7 +66,7 @@ npm run lint       # ESLint

 | Symptom | Cause | Fix |
 |---------|-------|-----|
-| "kube-vip Not Detected" | No kube-vip pods in kube-system | Install kube-vip per https://kube-vip.io/docs/installation/ |
+| "kube-vip Not Detected" | No kube-vip pods in kube-system namespace | Install kube-vip per https://kube-vip.io/docs/installation/ |
 | No IP pools shown | kubevip ConfigMap not found | Install kube-vip-cloud-provider |
 | Services show "Pending" VIP | No IP pool configured or pool exhausted | Add IP ranges to kubevip ConfigMap |
 | Leader shows "—" | No kube-vip leases found | Verify leader election is enabled (`vip_leaderelection=true`) |
@@ -21,6 +21,7 @@ import {
  isEgressEnabled,
  isKubeVipService,
  isPodReady,
+  KUBE_VIP_NAMESPACE,
  phaseToStatus,
 } from '../api/k8s';
 import { useKubeVipContext } from '../api/KubeVipDataContext';
@@ -105,7 +106,7 @@ export default function OverviewPage() {
              {
                name: 'Status',
                value: (
-                  <StatusLabel status="error">No kube-vip pods found in kube-system</StatusLabel>
+                  <StatusLabel status="error">No kube-vip pods found in {KUBE_VIP_NAMESPACE}</StatusLabel>
                ),
              },
              {
Author	SHA1	Message	Date
Chris Farhood	96b7ff0e24	fix: revert docs namespace to kube-system and use KUBE_VIP_NAMESPACE constant Revert namespace references from headlamp back to kube-system in docs since kube-vip workload runs in kube-system namespace (not headlamp which is the Headlamp plugin install namespace). Changes: - CLAUDE.md: revert data sources and key constants namespace - README.md: revert requirements line and troubleshooting table - SECURITY.md: revert plugin scope namespaces - OverviewPage.tsx: use KUBE_VIP_NAMESPACE constant instead of hardcoded string Fixes PRI-562	2026-05-04 20:27:09 +00:00
Chris Farhood	f4acf34ccc	chore: retrigger CI after base branch fix	2026-05-04 18:50:35 +00:00
Chris Farhood	4813f3c314	chore: retrigger CI (post workflow fix)	2026-05-04 18:49:46 +00:00
Chris Farhood	c83a8c775b	chore: retrigger CI Co-Authored-By: Paperclip <noreply@paperclip.ing>	2026-05-04 16:25:02 +00:00
Chris Farhood	1f2287489c	docs: redirect install namespace references from kube-system to headlamp Update documentation to reference the Headlamp plugin namespace (headlamp) instead of kube-system where kube-vip itself is deployed. Files changed (all docs only): - README.md: requirements, troubleshooting table - CLAUDE.md: data sources, key constants namespace - SECURITY.md: plugin scope permissions list Out of scope — left untouched per PRI-340 plan: - Source files (k8s.ts, KubeVipDataContext.tsx, OverviewPage.tsx) - Test helpers (test-helpers.tsx) — kube-system is the watched workload namespace - ADR 003 — describes kube-vip static pod fallback behavior, not install namespace Co-Authored-By: Paperclip <noreply@paperclip.ing>	2026-05-04 07:51:05 +00:00