- Check in your browser that you can access the argoCD UI: `https://argocd.idpbuilder.cnoe.io.local:8443/`
## Next step
Replace the Helm command with an Application CR. Something like (NOT TESTED):
yeah, this aligns well with the previous conversation in using Argo Apps for anything other than Argo CD and Argo Workflows that needs to be installed.
Suggestion
Remove the hard coded ingress yaml resources to use instead a helm chart deployed using argoCD
How to reproduce
make
./idpbuilder create --buildName local --recreate
helm upgrade --install ingress-nginx ingress-nginx --repo https://kubernetes.github.io/ingress-nginx --namespace ingress-nginx --create-namespace -f values.yaml
apiVersion: argoproj.io/v1alpha1 kind: Application metadata: name: ingress-nginx-helm namespace: argocd spec: destination: namespace: ingress-nginx server: "https://kubernetes.default.svc" source: chart: ingress-nginx repoURL: https://kubernetes.github.io/ingress-nginx targetRevision: 4.8.2 helm: releaseName: ingress-nginx values: | controller: allowSnippetAnnotations: true service: type: NodePort hostPort:
Use host ports 80 and 443
project: idpbuilder-embedded-gitserver syncPolicy: automated: prune: true selfHeal: true syncOptions: