You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Extend the KWOK deployer matrix to validate filesystem (Git-source) bundle round-trips for argocd and flux — not just the OCI lanes added in #843 / PR #956.
The Chainsaw layer validates the bundle's shape on disk; the KWOK OCI lanes validate that a controller can pull the bundle from an in-cluster OCI registry and reconcile (or for flux-oci, apply). What's still uncovered is filesystem-bundle round-trip: aicr bundle --output ./dir -> Git server -> Argo CD Application / Flux GitRepository -> reconcile.
This matters because production users frequently choose Git as their GitOps source. A regression in the argocd (non-OCI) deployer's app-of-apps.yaml shape, or the flux (non-OCI) deployer's gitrepo-*.yaml source CRs, would slip through current CI.
Proposed approach
Install a Gitea pod in the aicr-registry namespace as part of kwok/scripts/install-infra.sh, mirroring the in-cluster registry:2 pattern. Each KWOK matrix cell:
Push the bundle to http://gitea.aicr-registry.svc.cluster.local:3000/aicr/<recipe>.git.
Render an Argo CD Application (or Flux GitRepository + Kustomization) pointing at that URL.
Wait for sync gate (same terminal-pass framing as argocd-oci / flux-oci).
Two new matrix lanes: argocd-git and flux-git. Tier 1 + Tier 3 only (Tier 2 stays helm-only per ADR-008).
Effort estimate
~1-2 days of work plus likely a round of KWOK-fidelity iteration (the same shape of pattern-discovery the OCI lanes went through). Doubles the matrix size — ~32 new CI cells across the existing 16 recipes.
Notes
Gitea image is multi-arch and well-maintained; we can pin via .settings.yaml::testing_tools.gitea_image.
Repository-creds shapes for Argo CD (secret-type: repo-creds) and Flux (Secret referenced by GitRepository.spec.secretRef) are documented and well-understood.
Summary
Extend the KWOK deployer matrix to validate filesystem (Git-source) bundle round-trips for
argocdandflux— not just the OCI lanes added in #843 / PR #956.Motivation
Today's coverage after PR #956:
helmargocdbundle-variants)argocd-ocilane)argocd-helmbundle-dynamic)argocd-helm-ocilane)fluxbundle-flux)flux-oci)helmfilebundle-helmfile)The Chainsaw layer validates the bundle's shape on disk; the KWOK OCI lanes validate that a controller can pull the bundle from an in-cluster OCI registry and reconcile (or for
flux-oci, apply). What's still uncovered is filesystem-bundle round-trip:aicr bundle --output ./dir-> Git server -> Argo CDApplication/ FluxGitRepository-> reconcile.This matters because production users frequently choose Git as their GitOps source. A regression in the
argocd(non-OCI) deployer'sapp-of-apps.yamlshape, or theflux(non-OCI) deployer'sgitrepo-*.yamlsource CRs, would slip through current CI.Proposed approach
Install a Gitea pod in the
aicr-registrynamespace as part ofkwok/scripts/install-infra.sh, mirroring the in-clusterregistry:2pattern. Each KWOK matrix cell:aicr bundle --recipe ... --output ./bundle(filesystem output).http://gitea.aicr-registry.svc.cluster.local:3000/aicr/<recipe>.git.Application(or FluxGitRepository+Kustomization) pointing at that URL.argocd-oci/flux-oci).Two new matrix lanes:
argocd-gitandflux-git. Tier 1 + Tier 3 only (Tier 2 stays helm-only per ADR-008).Effort estimate
~1-2 days of work plus likely a round of KWOK-fidelity iteration (the same shape of pattern-discovery the OCI lanes went through). Doubles the matrix size — ~32 new CI cells across the existing 16 recipes.
Notes
.settings.yaml::testing_tools.gitea_image.secret-type: repo-creds) and Flux (Secret referenced byGitRepository.spec.secretRef) are documented and well-understood.Acceptance criteria
install-infra.shwhenDEPLOYERisargocd-gitorflux-git.argocd-gitlane added tokwok-recipes.yamlTier 1 + Tier 3.flux-gitlane added tokwok-recipes.yamlTier 1 + Tier 3.wait_for_argocd_sync/wait_for_flux_syncterminal-pass shape (no per-lane divergence).docs/contributor/kwok-testing.mdupdated with the new lanes.Related
argocd-oci,argocd-helm-oci,flux-oci)