nova

Nova service overlays for a site OpenStack Helm deployment.

Deployment Scope

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

How ArgoCD Builds It

• ArgoCD renders Helm chart nova and Kustomize path components/nova/.
• 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:
  nova:
    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 the Nova-specific chart or manifest values.
• nova-db-password Secret: Provide username and password for the Nova database user.
• nova-rabbitmq-password Secret: Provide username and password for the Nova messaging user.
• nova-nautobot Secret: Provide the rendered Nova-to-source-of-truth configuration that the service consumes. The current example delivers this as a single nova-nautobot.conf key.

Optional additions:

• Alternative secret sync resources: If that configuration Secret is generated by an external system, add only the generic sync resources needed to materialize the final Secret.

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 nova/values.yaml.