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
This commit is contained in:
2026-05-04 20:27:09 +00:00
committed by Gandalf the Greybeard [agent]
parent f4acf34ccc
commit 96b7ff0e24
5 changed files with 19863 additions and 9 deletions
+2 -2
View File
@@ -20,7 +20,7 @@ Search for `kube-vip` in the Headlamp Plugin Manager (Settings → Plugins → C
## Requirements
- Headlamp >= v0.26
- kube-vip deployed in `headlamp` (DaemonSet or static pod)
- kube-vip deployed in `kube-system` (DaemonSet or static pod)
- Optional: kube-vip-cloud-provider for IP pool management
## RBAC
@@ -66,7 +66,7 @@ npm run lint # ESLint
| Symptom | Cause | Fix |
|---------|-------|-----|
| "kube-vip Not Detected" | No kube-vip pods in headlamp namespace | 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`) |