Environment

Device and OS: RHEL 9.4
App version: `v0.42.0
Kubernetes distro being used: RKE2, 1.31.1+rke2r2

Steps to reproduce

1. Install fluxcd
2. Create gitrepo with the blow manifests
3. Wait for flux to re-apply the kustomization

Expected result

The .spec.url to point to the zarf docker registry

Actual Result

The .spec.url reverts back to the url to oci://registry1.dso.mil/bigbang

Comments

We do not have a builtin template for the registry IP, but I'd like to solve this without one.
Looks like the issue is that the Zarf agent checks for the zarf-agent: patched which is added during the initial mutation, and exits if it already exists. see this block.
I believe the mutation of every resource in the mutating webhook is idempotent, so we can just delete that check.

• Austin Abro, on Slack

Manifests

kustomization.yml

---
apiVersion: kustomize.toolkit.fluxcd.io/v1
kind: Kustomization
metadata:
  name: bigbang
  namespace: flux-system
spec:
  interval: 2m0s
  path: ./.
  prune: true
  sourceRef:
    kind: GitRepository
    name: flux-system

bigbang.yml

---
apiVersion: source.toolkit.fluxcd.io/v1
kind: HelmRepository
metadata:
  name: registry1
  namespace: flux-system
spec:
  interval: 2m
  type: oci
  url: oci://registry1.dso.mil/bigbang