* Install applicationset crd always
ApplicationSet is required by argocd-server, cannot be "opt-out".
If ApplicationSet CRD is not installed, we see lot of errors:
```
W0507 19:44:33.469804 7 reflector.go:424] pkg/mod/k8s.io/client-go@v0.26.11/tools/cache/reflector.go:169: failed to list *v1alpha1.ApplicationSet: the server could not find the requested resource (get applicationsets.argoproj.io)
E0507 19:44:33.469828 7 reflector.go:140] pkg/mod/k8s.io/client-go@v0.26.11/tools/cache/reflector.go:169: Failed to watch *v1alpha1.ApplicationSet: failed to list *v1alpha1.ApplicationSet: the server could not find the requested resource (get applicationsets.argoproj.io)
```
Signed-off-by: Thomas Decaux <ebuildy@gmail.com>
* Bump chart version
Signed-off-by: Thomas Decaux <ebuildy@gmail.com>
* Bump Chart.yaml patch version
Signed-off-by: Thomas Decaux <ebuildy@gmail.com>
* Update Chart.yaml changelog
Signed-off-by: Thomas Decaux <ebuildy@gmail.com>
---------
Signed-off-by: Thomas Decaux <ebuildy@gmail.com>
Co-authored-by: Petr Drastil <petr.drastil@gmail.com>
Co-authored-by: yuki.kitakata <yu.croco@gmail.com>
feat(argo-cd): Add ability to add additional labels to all CRDs via .Values.crds.additionalLabels
Signed-off-by: jdvgh <133217951+jdvgh@users.noreply.github.com>
* [charts/argo-cd] Update to 1.3, some chart cleanup
* Bumps the version of ArgoCD to 1.3 and the chart version to 1.2 due
to a CRD change. Restored conditional CRDs to correct #27. Additionally,
some value defaults were added so Helm strict linting could pass.
* This adds some examples to the values.yaml on how to use the new
Helm repo chart types. Add helmignore to help with development.
The argocd application expects that the label 'app.kubernetes.io/part-of' is set to 'argocd' otherwise the configmap or secret is rejected, and the argocd-dex-server, argocd-server, and argocd-application-controller fail to start.
* Add application controller resources
First chart version for argo-cd
added the new labels recommeneded for k8
* Add repo server resources
Use legacy label and new one for application controller selectors
Set labels for deployment for easier discovery
* Configure git repositories, helm chart museums and dex connectors
This way argo-cd could be configured to update itself via helm
* Parameterize the rbac configmap
* Parameterize webhook secrets
* Parameterize server deployment and set services with the labels
* Add service account, role and rolebinding for server deployment
* Clean the old label, use only latest recommendations
Follow the ideas and changes of https://github.com/argoproj/argo-cd/pull/1035
* Fix var naming issues
* Fix server service incorrect ports
* Install crds with helm hook
* Enable cluster admin accessby default
Default installation will allow installing apps in the current cluster without
inputted credentials. For other clusters inputted credentials will be needed
* Parameterize the dex server
* Harcode resource names because code expects them this way
Some resource names and application urls are hardcoded in code with these
names. So they can't be parameterized.
* Create the ingress with tls passthrough support
Tls is terminated on the ArgoCD server, not on ingress
* Fix typo on application controller sa
* Add notes on how to connect to server UI after installation
