privilegedescalation-ceo[bot]
e2ae92648c
* docs: update Headlamp install namespace references from kube-system to headlamp Updates all documentation references to the Headlamp install namespace from kube-system to headlamp as part of PRI-433. In-scope files updated: - README.md, SECURITY.md - docs/getting-started/installation.md, quick-start.md, prerequisites.md - docs/deployment/helm.md, kubernetes.md, production.md - docs/troubleshooting/README.md, common-issues.md, rbac-issues.md - docs/user-guide/configuration.md, rbac-permissions.md - docs/TESTING.md, TROUBLESHOOTING.md, DEPLOYMENT.md Out-of-scope (unchanged): - Source files referencing upstream workload namespace - RBAC manifests describing Polaris namespace (polaris ns is unchanged) - NetworkPolicy namespaceSelector (API server runs in kube-system) - design-decisions.md and ARCHITECTURE.md (URL hashes refer to cluster namespaces, not Headlamp install ns) Co-Authored-By: Paperclip <noreply@paperclip.ing> * fix: correct RBAC manifest per QA review (PRI-555) - Remove rbac.authorization.k8s.io privilege escalation block - Fix orphaned comment from round 1 - Add EOF newline - Keep serviceaccounts/token for E2E auth (confirmed needed) - Namespace already correct (privilegedescalation-dev) Co-Authored-By: Paperclip <noreply@paperclip.ing> * docs: replace hardcoded namespace with <your-namespace> placeholder Users choose their own namespace for Headlamp. Replace all hardcoded namespace references (headlamp, kube-system) in user-facing docs with <your-namespace> so users substitute their own value. Conventions: - Helm install: --namespace <your-namespace> --create-namespace - kubectl commands: -n <your-namespace> - YAML metadata: namespace: <your-namespace> - Prose: "the namespace where Headlamp is installed" Out-of-scope references left untouched: - kube-system in NetworkPolicy selectors (API server namespace) - polaris namespace references (upstream workload namespace) - Source code and test files Refs: PRI-433 Co-Authored-By: Paperclip <noreply@paperclip.ing> * docs: fix remaining hardcoded headlamp namespace to <your-namespace> placeholder Prior commit was inconsistent — some files used <your-namespace> while DEPLOYMENT.md, TROUBLESHOOTING.md and several troubleshooting/user-guide docs still hardcoded headlamp as the namespace. Co-Authored-By: Paperclip <noreply@paperclip.ing> --------- Co-authored-by: Chris Farhood <chris@farhood.org> Co-authored-by: Paperclip <noreply@paperclip.ing>
Documentation
Central hub for Headlamp Polaris Plugin documentation.
Quick Links
Getting Started
New to the Headlamp Polaris Plugin? Start here:
- Prerequisites - System requirements, Headlamp version, Polaris installation
- Installation - Four installation methods: Plugin Manager, Sidecar, Manual, Source
- Quick Start - Get up and running in 5 minutes
User Guide
Learn how to use the plugin:
- Features - Overview dashboard, namespace views, inline audits, exemption management
- Configuration - Refresh intervals, dashboard URLs, settings
- RBAC Permissions - Required permissions, service proxy access, token-auth mode
Troubleshooting
Having issues? Check here:
- Quick Diagnosis - Quick reference table for common symptoms
- Common Issues - Detailed resolution steps for frequent problems
- RBAC Issues - Permission debugging, 403 errors, token-auth
- Network Problems - NetworkPolicies, connectivity, proxy issues
Architecture
Understand how the plugin works:
- Overview - High-level architecture, component hierarchy
- Data Flow - How data moves from Polaris to the UI
- Design Decisions - Key architectural choices and rationale
- ADRs - Architecture Decision Records
Development
Contributing to the plugin:
- Development Workflow - Setup, building, hot reload
- Testing - Unit tests, E2E tests, CI/CD
- Code Style - TypeScript, React, linting, formatting
- Release Process - Versioning, changelog, GitHub Actions
Deployment
Production deployment guides:
- Kubernetes - Direct Kubernetes manifest deployment
- Helm - Helm chart configuration, values
- Production Checklist - RBAC, NetworkPolicies, security, monitoring
API Reference
- polaris.ts - JSDoc-annotated TypeScript API (data fetching, types, utilities)
- PolarisDataContext.tsx - React Context provider for shared data
Need help? Open an issue on GitHub or check CONTRIBUTING.md for development guidelines.