forust
d85bdf5dbd
ci / Compose (pull_request) Successful in 27s
ci / Workflows (pull_request) Successful in 14s
ci / Shell (pull_request) Successful in 34s
ci / Python and tests (pull_request) Successful in 19s
ci / YAML (pull_request) Successful in 17s
ci / Dockerfiles (pull_request) Successful in 6s
ci / Formatting (pull_request) Successful in 36s
ci / Kubernetes (pull_request) Successful in 14s
ci / image-plan (pull_request) Skipped
ci / Image (${{ matrix.name }}) (pull_request) Skipped
ci / build (pull_request) Skipped
renovate-ci / validate-renovate (pull_request_target) Successful in 3m13s
Homarr
Dashboard with Kubernetes integration and persistent application state.
Kubernetes uses the homarr ServiceAccount and the read-only ClusterRole in
k8s/rbac.yaml. Application data lives in homarr-pvc; supply the encryption key
from k8s/secrets.yaml.example before the first start and retain it with backups.
The committed ingress is internal. There is no k8s/active marker even though
manifests exist, so the workflow does not select Homarr automatically.
Compose publishes ports 80 and 81, mounts appdata and the Docker socket, and expects a local kubeconfig. Check these host ports against Traefik before use.
Inspect
From the repository root:
kubectl get pods,svc,pvc -n homarr
kubectl get events -n homarr --sort-by=.metadata.creationTimestamp
See the repository README for deployment selection.