horizon

Horizon dashboard overlays for a site OpenStack Helm deployment.

Deployment Scope

• Cluster scope: site
• Values key: site.horizon
• ArgoCD Application template: charts/argocd-understack/templates/application-openstack-helm.yaml

How ArgoCD Builds It

• ArgoCD renders Helm chart horizon and Kustomize path components/horizon/.
• The shared site-level secret-openstack.yaml and optional images-openstack.yaml files are loaded before the service-specific values file.
• The deploy repo contributes values.yaml for this component.
• The deploy repo overlay directory for this component is applied as a second source, so kustomization.yaml and any referenced manifests are part of the final Application.

How to Enable

Enable this component under the scope that matches your deployment model:

$CLUSTER_NAME/deploy.yaml

site:
  horizon:
    enabled: true

Deployment Repo Content

Use any secret delivery mechanism you prefer. The contract that matters is the final Kubernetes Secret or manifest shape described below.

Required or commonly required items:

• values.yaml: Provide dashboard-specific Helm values such as ingress, branding, or endpoint settings.
• horizon-db-password Secret: Provide username and password for the Horizon database user.

Optional additions:

• Additional auth or ingress resources: Add them here if you need dashboard-specific integrations beyond the chart values.

Notes

• This service is rendered by application-openstack-helm.yaml, which also reads the shared site-level secret-openstack.yaml and optional images-openstack.yaml files before it reads horizon/values.yaml.