Skip to content

openstack-sync-plugins

Deploys OpenStack sync custom resources as Kustomize/raw YAML.

It does not ship CRDs, hook code, or operator RBAC. CRDs and hook execution are owned by
openstack-sync-operator; this Application applies the CRs that hooks read.

Enable the Application with site.openstack_sync_plugins.enabled.

Deployment Scope

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

How ArgoCD Builds It

  • ArgoCD renders Kustomize path components/openstack-sync-plugins.
  • The current template does not read a deploy-repo 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.

Deployment Repo Content

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

Shared Neutron router flavor CRs that should apply to all clusters live in the
understack repo under:

components/openstack-sync-plugins/neutron-router-flavors/

The shared data entrypoint is:

components/openstack-sync-plugins/kustomization.yaml

Cluster-specific CRs live in the deployment repo under
<deploy-repo>/<site>/openstack-sync-plugins/ and are listed by that directory's
kustomization.yaml.

Hook enablement is separate. Set plugins.neutronRouterFlavors: true in
<deploy-repo>/<site>/openstack-sync-operator/values.yaml only after the site
is pinned to an operator image built with /hooks/router_flavors.py.

plugins.neutronRouterFlavors: false does not stop this Application from
creating NeutronRouterFlavor CRs. It only disables the operator hook that
reconciles those CRs into OpenStack. To stop creating the CRs, disable
site.openstack_sync_plugins.enabled or remove the CR files from the relevant
kustomization.yaml.

Neutron router flavor CR files use the published editor schema
schema/openstack-sync/neutron-router-flavor.schema.json. That schema validates
the flavor data under spec, not the Kubernetes wrapper fields. Kubernetes
validates required fields, types, enums, and defaults through the operator-owned
CRD when ArgoCD applies the CR. The editor schema is stricter about unknown spec
fields, so add new schema fields with the matching operator hook/CRD change when
a driver needs new service-profile data.