GitRepository and Kustomization are not installed when we do helm release or kubectl apply the first time. about helm-charts HOT 7 CLOSED

@suryapandian Helm can't upgrade CRDs if they are placed in the /crds dir, We release CRD updates with every Flux release, so to overcome this Helm limitation we had to place the CRDs in /templates.

from helm-charts.

This is the expected behavior, you need to use the flux2-sync chart to create GitRepostories and Kustomizations after you’ve installed flux2.

from helm-charts.

I am having both flux2 and flux2-sync as dependencies in the chart. If flux2-sync had a helm hook that waited until the CRD was installed, I will be able to do

helm upgrade --install flux2 ./charts/flux2

instead of doing the multipline commands

helm template flux-capacitor ./charts/flux2  \
      --namespace flux2 \
      --values ./tests/flux2/values.yaml \
      --output-dir ./tests/artifacts
kubectl apply -Rf ./tests/artifacts/flux2/charts/flux2
kubectl apply -Rf ./tests/artifacts/flux2/charts/flux2-sync

I am not able to do helm upgrade --install flux2 ./charts/flux2 because gitrepositories and kustomizations is tried to get applied before the CRDs are installed.

from helm-charts.

I am having both flux2 and flux2-sync as dependencies in the chart.

You can't do that, you need to run them one after the other.

from helm-charts.

Also what's the point of using Helm with kubectl? Please see flux bootstrap that does all things for you.

from helm-charts.

I am having both flux2 and flux2-sync as dependencies in the chart.

You can't do that, you need to run them one after the other.

Okay, will do it one after another.
Could you please point me to a doc that would help me understand why I cannot do that?

from helm-charts.

hmm thanks Stefan, will read along these.

from helm-charts.