the setup for the experiment

We're doing a little Git-less Flux. This may not be advisable. Note the
"DO NOT EDIT" klaxon at the top of this file.

"# I was warned" says it all.

https://fluxcd.io/flux/installation/configuration/boostrap-customization/
for the best-practices way to do this type of customization, we are in
uncharted territory using Flux manifests with OCI in a Git-less way.

Signed-off-by: Kingdon Barrett <[email protected]>

Author: kingdonb

README.md

@@ -117,7 +117,9 @@ then you may simply need to [annotate the nodes](https://github.com/KWasm/kwasm-
 If you get this error:
 
 ```
-...
+✔ component manifests are up to date
+► installing components in "flux-system" namespace
+✗ Kustomization/flux-system/flux-system dry-run failed: no matches for kind "Kustomization" in version "kustomize.toolkit.fluxcd.io/v1"
 ```
 
 ...Then either I forgot to clean up after my experiments in `flux-system`, or

clusters/cozy-test/flux-system/gotk-sync.yaml

@@ -25,3 +25,34 @@ spec:
   sourceRef:
     kind: GitRepository
     name: flux-system
+# I was warned
+---
+apiVersion: kustomize.toolkit.fluxcd.io/v1
+kind: Kustomization
+metadata:
+  name: flux-oci
+  namespace: flux-system
+spec:
+  interval: 10m0s
+  path: ./
+  prune: true
+  sourceRef:
+    kind: OCIRepository
+    name: flux-oci
+  patches:
+  - patch: |
+      - op: add
+        path: /spec/template/spec/containers/0/args/-
+        value: --concurrent=10
+      - op: add
+        path: /spec/template/spec/containers/0/args/-
+        value: --requeue-dependency=5s
+      - op: replace
+        path: /spec/template/spec/containers/0/resources/limits/cpu
+        value: "2"
+      - op: replace
+        path: /spec/template/spec/containers/0/resources/limits/memory
+        value: "2Gi"
+    target:
+      kind: Deployment
+      name: "(kustomize-controller|helm-controller|source-controller)"