But another little caveat is knowing what there is to kustomize there... but I guess there could be a gitignored folder to dump to while trying to kustomize things..
It's a pity replicated/ship project isn't really being updated, I used that for this purpose in the past.
and I point two argo apps one to dev and the other to prod, that's really the point of kustomize for me, is apart the final mile touches, I can configure for different environments... so I used to use replicated/ship to turn the helm chart into kustomize, and then I would add the overlays -- but they're not really updating that tool anymore. So with your technique, I could adapt it to what I wrote above. Unless you have some better advice for this?
Nice article, thanks! Just wondering how could we could point the app to kustomized dev/prod overlays?
I guess:
helm template ../../ --name-template $ARGOCD_APP_NAME --namespace $ARGOCD_APP_NAMESPACE --include-crds > ../../all.yaml && kustomize build
But another little caveat is knowing what there is to kustomize there... but I guess there could be a gitignored folder to dump to while trying to kustomize things..
It's a pity replicated/ship project isn't really being updated, I used that for this purpose in the past.
Wait could you explain what this post is about?
Sorry, I mean my desired kustomize setup would be:
[chart files...]
all.yaml
overlays/
|_dev/...
|_prod/...
and I point two argo apps one to dev and the other to prod, that's really the point of kustomize for me, is apart the final mile touches, I can configure for different environments... so I used to use replicated/ship to turn the helm chart into kustomize, and then I would add the overlays -- but they're not really updating that tool anymore. So with your technique, I could adapt it to what I wrote above. Unless you have some better advice for this?
No, I didn't know that kustomize existed until today. After reading some of this I've genuinely been enlightened.