A lightweight Kubernetes dashboard where the user's identity reaches the API server
Documentation | Architecture | Differences from Kite
English | 中文
Lightkite is an independent fork of Kite. It keeps Kite's Kubernetes UI and replaces its local identity, local authorization, and shared privileged kubeconfigs with standard OpenID Connect and Kubernetes-native RBAC. The browser signs in through the configured OIDC provider; Lightkite sends that user's validated ID token to the selected Kubernetes API server. Configured group claims therefore map directly to Kubernetes RoleBindings and ClusterRoleBindings.
Lightkite is installed as a new deployment. An existing Kite installation is not a supported in-place upgrade source.
See the OIDC Kubernetes architecture and the detailed
comparison with upstream Kite. Provider-specific
configuration belongs under examples/ and never enters the core runtime.
The backend also provides a transparent Kubernetes API gateway
for moving UI data access onto canonical Kubernetes resource APIs.
- Dark/light/color themes with system preference detection
- Global search across all resources
- Responsive design for desktop, tablet, and mobile
- i18n support (English and Chinese)
- Switch between multiple Kubernetes clusters
- Kubernetes-authorized in-cluster Prometheus service proxy per cluster
- Credential-free HTTPS Kubernetes endpoint connectivity
- Add, edit, switch, and remove credential-free cluster catalog entries
- Full coverage: Pods, Deployments, Services, ConfigMaps, Secrets, PVs, PVCs, Nodes, and more
- Live YAML editing with Monaco editor (syntax highlighting and validation)
- Detailed views with containers, volumes, events, and conditions
- Resource relationships (e.g., Deployment → Pods)
- Create, update, delete, scale, and restart operations
- Custom Resource Definitions (CRDs) support
- Quick image tag selector using Docker and container registry APIs
- Helm chart discovery, install, upgrade, rollback, and release management
- Customizable sidebar with CRD shortcuts
- Kube proxy for direct pod/service access (no more
kubectl port-forward)
- Real-time CPU, memory, and network charts (Prometheus)
- Live pod logs with filtering and search
- Pod logs and workload metrics, subject to Kubernetes RBAC
- Provider-neutral OIDC Authorization Code + PKCE login
- Server-side encrypted OIDC sessions; no tokens exposed to browser JavaScript
- Configurable group claims mapped directly by the Kubernetes API server
- Kubernetes-native RBAC as the sole resource authorization policy
- No stored kubeconfig, bearer token, client certificate, or privileged ServiceAccount
For detailed instructions, see the installation guide.
Configure the required OIDC and secret values described in docs/oidc-kubernetes.md. Startup fails closed if they are absent or use the upstream development defaults.
-
Install the versioned OCI chart published by Lightkite
helm install lightkite oci://ghcr.io/realmroot/charts/lightkite \ --version <version> -n lightkite-system --create-namespace -f values.yaml
-
Or install from Helm repository
helm repo add lightkite https://realmroot.github.io/lightkite/ helm repo update helm install lightkite lightkite/lightkite --version <version> \ -n lightkite-system --create-namespace -f values.yaml
-
Apply deployment manifests
kubectl apply -f deploy/install.yaml # Release assets contain the same manifest with an immutable image tag. curl -fLO https://github.com/realmroot/lightkite/releases/download/vX.Y.Z/install.yaml $EDITOR install.yaml kubectl apply -f install.yaml
-
Access via port-forward
kubectl port-forward -n lightkite-system svc/lightkite 8080:8080
-
Clone the repository
git clone https://github.com/realmroot/lightkite.git cd lightkite -
Build the project
make deps make build
-
Run the server
make run
For troubleshooting, see the local FAQ and configuration guides.
We welcome contributions! Please see our contributing guidelines for details on how to get involved.
Lightkite is based on Kite and remains grateful to its maintainers and contributors for the dashboard, resource views, and interaction model that made this fork possible. Lightkite is independently maintained, is not affiliated with or endorsed by the upstream project, and does not plan to merge this architecture fork back into Kite as a whole. Focused fixes may still be shared with upstream when they are generally useful.
This project is licensed under the Apache License 2.0 - see the LICENSE file for details.