Files
2026-08-31 10:57:52 -04:00
..
2025-08-04 15:52:51 -04:00
2026-08-31 10:57:52 -04:00
2026-08-31 10:57:52 -04:00
2025-08-04 15:23:35 -04:00

homepage

A Helm chart that deploys Homepage, a self-hosted dashboard / start page, with the RBAC it needs to read cluster state.


What it creates

  • ConfigMap homepage — home directory-style config files populated with a default Kubernetes widget and empty settings.yaml, services.yaml, bookmarks.yaml, custom.css, custom.js.
  • Deployment homepage — runs the Homepage container (ports 3000), mounts the ConfigMap entries (and an emptyDir for logs).
  • Service homepage — exposes the dashboard on port 80 → 3000.
  • ServiceAccount + Secret homepage (service-account-token).
  • ClusterRole / ClusterRoleBinding homepage — allows reading namespaces/pods/nodes/services/endpoints, ingresses, Traefik ingressroutes, Gateway API httproutes/gateways, and metrics (metrics.k8s.io). This powers the cluster widgets and enables services to be discovered via the gethomepage.dev/* annotations added by the compose-app ingresses.

values.yaml reference

Key Default Description
image ghcr.io/gethomepage/homepage:latest Homepage container image.
allowedHosts gethomepage.dev Value for the HOMEPAGE_ALLOWED_HOSTS env var.
serviceType ClusterIP Type of the homepage Service.
serviceAnnotations {} Annotations applied to the Service.

Notes

  • The ConfigMap contents are hardcoded in the template; to customize settings.yaml, services.yaml, bookmarks.yaml, or custom.*, edit the configmap.yaml template (or override it) — they are not parameterized via values.yaml.
  • The homepage <release> install typically pairs with ingresses from compose-app whose gethomepage.dev annotations are picked up automatically because Homepage runs in mode: cluster.