Using ArgoCDInstance

See the ArgoCDInstance resource reference for the API, example, and field definitions.

Catalog defaults

Every target emits a parent Application named <target>-catalog unless DeploymentTarget.spec.catalogApplication.enabled is false. The parent recursively syncs <pathPrefix>/_nyl/catalog and therefore manages the generated child Applications, AppProjects, and its own manifest.

Nyl’s catalog defaults apply without any explicit policy configuration:

• Manual synchronization.
• ApplyOutOfSyncOnly=true and ServerSideApply=true for synchronization.
• applicationDeletionPolicy: Foreground, so deleting the parent cascades to catalog resources.
• selfPrunePolicy: Confirm, which annotates the parent with Prune=confirm.

Set ArgoCDInstance.spec.catalogApplicationDefaults to customize these defaults for its targets. An individual DeploymentTarget can override the name, project, sync policy, deletion policy, self-prune policy, labels, and annotations under spec.catalogApplication.

Enable automated catalog synchronization explicitly when the publication workflow provides the required approval boundary:

spec:
  catalogApplicationDefaults:
    syncPolicy:
      automated:
        enabled: true
        prune: false
        selfHeal: true
      syncOptions:
        - ApplyOutOfSyncOnly=true
        - ServerSideApply=true

When no ArgoCDInstance resources exist, each target gets an implicit local instance using its workload Cluster, the argocd namespace, and these defaults. --verbose logs that choice. Once any explicit instance exists, every target must set spec.argocdRef.name; this prevents accidental attachment to the wrong control plane.

The default AppProject must exist before the catalog can manage itself. After rendering and publishing a target for the first time, seed its parent once:

kubectl apply -f deploy/<target>/_nyl/catalog/application.argoproj.io/argocd/<target>-catalog.yaml

Use the actual rendered output path and configured namespace when they differ.