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 emptysettings.yaml,services.yaml,bookmarks.yaml,custom.css,custom.js. - Deployment
homepage— runs the Homepage container (ports3000), mounts the ConfigMap entries (and anemptyDirfor 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, Traefikingressroutes, Gateway APIhttproutes/gateways, and metrics (metrics.k8s.io). This powers the cluster widgets and enables services to be discovered via thegethomepage.dev/*annotations added by thecompose-appingresses.
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, orcustom.*, edit theconfigmap.yamltemplate (or override it) — they are not parameterized viavalues.yaml. - The
homepage <release>install typically pairs with ingresses fromcompose-appwhosegethomepage.devannotations are picked up automatically because Homepage runs inmode: cluster.