I think the example here would just work
# spicedbe
ecordell
08/16/2023, 6:21 PMI think the example here would just work:
https://fluxcd.io/flux/components/kustomize/kustomization/
the kustomize manifests live here: https://github.com/authzed/spicedb-operator/tree/main/config so you should be able to point the GitRepository at that directory and then point a Kustomization object at that
you may want to pin to a specific release with the images option though: https://fluxcd.io/flux/components/kustomize/kustomization/#images
j
jawnsyy
08/16/2023, 6:27 PMAhh, I see. We only install our own stuff via GitRepository currently (everything else is installed via HelmRepository/HelmRelease) so this process is a bit unusual for us
jawnsyy
08/16/2023, 6:52 PMActually, maybe I want to give this installation method a try? Adding a Kustomization w/ resources? https://github.com/authzed/spicedb-operator/releases/tag/v1.8.0
jawnsyy
08/16/2023, 6:52 PMWe usually follow tagged releases and use updatecli to update stuff so that seems like a better way to go
jawnsyy
08/16/2023, 6:58 PMMaybe I'm getting mixed up between the Flux Kustomization and Kubernetes Kustomization heh
jawnsyy
08/16/2023, 8:00 PMI definitely think an officially-published Helm chart would be more natural for us, FWIW. I see there's an open issue for that already.
One tricky thing is that we need to load the GitRepository and also update the image pin via newTag, so updatecli needs to handle both for us
3 Views