Summary

Add a flux deployer type to the bundler, enabling generation of Flux CD deployment artifacts (HelmRelease, Kustomization, GitRepository sources) alongside the existing helm, argocd, and argocd-helm deployers.

Motivation

AICR currently supports three deployer types: helm (default), argocd, and argocd-helm. Organizations using Flux CD as their GitOps controller have no native bundle output — they must manually translate Helm bundles into Flux CRDs. A first-class flux deployer would close this gap and align AICR with the two dominant GitOps ecosystems (ArgoCD and Flux).

Scope

New deployer: pkg/bundler/deployer/flux/

Implement the deployer.Deployer interface (Generate(ctx, outputDir) (*Output, error)) producing:

Registration changes

Config options to support

• --repo-url and --target-revision (reuse existing config fields, same as ArgoCD)
• --dynamic support TBD — may follow the argocd-helm pattern with valuesFrom / postBuild.substituteFrom

Flag compatibility (pre-flight validation in buildDeployer)

Output structure (proposed)

output/
├── README.md
├── kustomization.yaml          # Root Kustomization referencing all resources
├── sources/
│   ├── helmrepo-<name>.yaml    # HelmRepository per unique chart repo
│   └── gitrepo-<name>.yaml     # GitRepository per unique Git source
├── cert-manager/
│   ├── helmrelease.yaml        # HelmRelease CR (dependsOn ordering)
│   └── values.yaml             # Helm values (inline or ConfigMap)
└── gpu-operator/
    ├── helmrelease.yaml
    └── values.yaml

Implementation notes

• Follow the existing deployer pattern: struct with exported fields, compile-time interface check (var _ deployer.Deployer = (*Generator)(nil))
• Use shared helpers from pkg/bundler/deployer/helpers.go (SafeJoin, WriteValuesFile, GenerateFromTemplate, SortByDeploymentOrder)
• Deployment ordering maps to dependsOn in HelmRelease/Kustomization CRs (analogous to ArgoCD sync-waves)
• Flux API versions: source.toolkit.fluxcd.io/v1 and helm.toolkit.fluxcd.io/v2 (stable APIs)
• Kustomize components use Kustomization CR pointing to GitRepository source with path/tag

Test plan

• Unit tests for flux.Generator.Generate() covering Helm, Kustomize, and mixed-component recipes
• Table-driven tests for HelmRelease and Kustomization CR generation
• Verify dependsOn ordering matches recipe deployment order
• Verify flag incompatibility errors (--attest, --data)
• E2E: aicr bundle --deployer flux produces valid Flux CRDs (YAML schema validation)
• Update ParseDeployerType and GetDeployerTypes tests