Chris Farhood
96b7ff0e24
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
25 lines
644 B
Markdown
25 lines
644 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 `kube-system`
|
|
- DaemonSets in `kube-system`
|
|
- Leases in `kube-system`
|
|
- ConfigMaps in `kube-system`
|
|
|
|
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.
|