Stefan Prodan
Stefan Prodan
Not asking you to upgrade all of them, just one to rerun the test. We've tried to replicate this with 2.0.1 and the HelmRepository is not getting stuck. Also what...
It wold also be helpful if you can post here `kubectl get helmrepository --show-managed-field -oyaml` for the one that's stuck.
If you run `flux reconcile helmrepository` does it find the secret or the same thing happens?
This is really strange, is your Kubernetes API under heavy load, is etcd having any issue? This may be a caching issue, we have disabled the caching of Secrets in...
Could you also switch to Wolfi from distroless? Thanks! Ref: https://github.com/stefanprodan/kustomizer/blob/main/Makefile#L75
It's `docker container run --rm ghcr.io/stefanprodan/kustomizer:v2.2.1 /kustomizer`
Ok let’s do this part of #83
I vote for Option 1. I would not want to maintain a dedicated CRD for Notation in Flux, as this would mean creating CRDs for cosign, openpgp, gitsign, sshsign, etc....
The ConfigMap and the HelmRelease can be applied by the same Flux Kustomization and there is no problem with ordering, see the docs: https://fluxcd.io/flux/guides/helmreleases/#refer-to-values-in-configmaps-generated-with-kustomize
The user-case you described above can be accomplished with kustomize configMap generators, each team would push their own values file to the repo where the HelmRelease is defined. All Flux...