#208. Initial flux package creation. Currently was able to deploy wit…

…h package-deploy and have the flux resources populate within kind cluster.

packages/flux/flux.sha256

@@ -0,0 +1 @@
+d2bbbee7cea42d9b513737a7a1a002fbc9ed18fcc8e10b91eee673b73336b010  zarf-package-flux.tar.zst

packages/flux/template/values.yaml

@@ -0,0 +1,15 @@
+registryCredentials:
+  - registry: "registry1.dso.mil"
+    username: "zarf-git-user"
+    password: "###ZARF_REGISTRY_AUTH_PULL###"
+  - registry: "docker.io"
+    username: "zarf-git-user"
+    password: "###ZARF_REGISTRY_AUTH_PULL###"
+  - registry: "registry.dso.mil"
+    username: "zarf-git-user"
+    password: "###ZARF_REGISTRY_AUTH_PULL###"
+
+flux:
+  interval: 1m
+  rollback:
+    cleanupOnFail: false

packages/flux/zarf.yaml

@@ -0,0 +1,20 @@
+kind: ZarfPackageConfig
+metadata:
+  name: flux
+  description: "Zarf flux package."
+
+components:
+  - name: baseline
+    required: true
+    secretName: "private-registry"
+    manifests:
+      - name: flux-installer
+        # This will be built on the package create side and deployed as a regular manifest on package deploy
+        kustomizations:
+          - https://repo1.dso.mil/platform-one/big-bang/bigbang.git//base/flux?ref=1.17.0
+    images:
+      # Flux images
+      - registry1.dso.mil/ironbank/fluxcd/helm-controller:v0.11.0
+      - registry1.dso.mil/ironbank/fluxcd/kustomize-controller:v0.13.0
+      - registry1.dso.mil/ironbank/fluxcd/notification-controller:v0.15.0
+      - registry1.dso.mil/ironbank/fluxcd/source-controller:v0.14.0