Chris Farhood
50338ad7c4
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>
25 lines
632 B
Markdown
25 lines
632 B
Markdown
# Security Policy
|
|
|
|
## Supported Versions
|
|
|
|
| Version | Supported |
|
|
|---------|-----------|
|
|
| latest | Yes |
|
|
|
|
## Plugin Scope
|
|
|
|
This plugin is **read-only**. It does not perform any write operations against the Kubernetes cluster. It reads:
|
|
|
|
- Services (type: LoadBalancer)
|
|
- Nodes
|
|
- Pods in `headlamp`
|
|
- DaemonSets in `headlamp`
|
|
- Leases in `headlamp`
|
|
- ConfigMaps in `headlamp`
|
|
|
|
All data is fetched through Headlamp's built-in API proxy, which respects the user's existing RBAC permissions.
|
|
|
|
## Reporting a Vulnerability
|
|
|
|
Please report security vulnerabilities by opening a private issue or emailing the maintainers directly.
|