Christopher Haar
Christopher Haar
in other communities the workflow is to create a seperate community repo to maintain the helm-chart - is this a option here ?
we use it like this: in chart flux2: ``` kustomizecontroller: secret: create: true name: netrc data: .netrc: "machine gitlab.com \nlogin git \npassword password" ## multiline via \n extraSecretMounts: - name:...
from aws-provider perspective we create a connection-secret with a kubeconfig inside - you can use this connection-secret to interact with provider-helm to said clusters - is this not working for...
@ChrisJBurns you can use flux2 helm-chart https://github.com/fluxcd-community/helm-charts/tree/main/charts/flux2 and flux2-sync helm-chart https://github.com/fluxcd-community/helm-charts/tree/main/charts/flux2-sync with provider-helm
Check this closed PR https://github.com/upbound/platform-ref-aws/pull/60 we using it like this in our production environment
You can mount all the stuff like ssh-keys, known-hosts, .netrc as Secrets / ConfigMaps - to source-controller - you can ping me as well on slack
can you say something when we can see PR merge ?
you can check: https://github.com/crossplane-contrib/provider-aws/blob/master/cluster/local/integration_tests.sh
@eloo thank for opening https://github.com/crossplane/crossplane/issues/2954 we faced today the same for automatic - that the revision number is not updated