Use k8s resources instead of "flux create" command
In install/install-openappstack.sh
we use two flux create commands:
flux create source git openappstack \
--url=https://open.greenhost.net/openappstack/openappstack \
--branch=master \
--interval=1m
flux create kustomization openappstack \
--source=GitRepository/openappstack \
--path="./flux2/cluster/base" \
--prune=true \
--interval=10m
Both only create k8s resources, i.e. the latter one creates:
$ kc -n flux-system get kustomizations.kustomize.toolkit.fluxcd.io openappstack -o yaml | yq eval '.spec' -
force: false
interval: 10m0s
path: ./flux2/cluster/base
prune: true
sourceRef:
kind: GitRepository
name: openappstack
it would be easier for me to understand what's going on behind the scenes if I could look at the k8s resource which is applied that to a flux2 meta-command.
To debug:
flux create --export ...
shows you the manifest that gets applied (without applying it)