Files
homarr/apps/docs/docs/integrations/kubernetes/index.mdx
T

45 lines
1.4 KiB
Plaintext

---
title: "Kubernetes"
description: "Read Kubernetes resources and cluster metrics in Homarr."
hide_title: true
---
import { IntegrationHeader } from "@site/src/components/integrations/header";
import { IntegrationCapabilites } from "@site/src/components/integrations/widgets";
import { kubernetesIntegration } from ".";
<IntegrationHeader integration={kubernetesIntegration} categories={["Containers"]} />
Homarr provides a read-only view of pods, services, ingresses, nodes, ConfigMaps, Secrets, namespaces, and volumes.
Metrics Server is optional; without it, inventory and reserved capacity remain available but live CPU and memory do not.
## In-cluster access
Enable RBAC in the Homarr Helm values:
```yaml
rbac:
enabled: true
```
The chart creates the service account and read-only Role/ClusterRole bindings used by Homarr. Kubernetes 1.24 or newer is
required.
## Kubeconfig contexts
When Homarr runs outside the cluster, mount a kubeconfig read-only and set `KUBECONFIG` to its in-container path:
```yaml
services:
homarr:
volumes:
- ./kubeconfig:/app/config/kubeconfig:ro
environment:
KUBECONFIG: /app/config/kubeconfig
```
The management page exposes every configured context. An unavailable context does not hide healthy contexts; a context
without Metrics Server is marked **Metrics unavailable**.
Kubernetes resources are not converted into Homarr apps or integrations during Docker discovery.