You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
upgrade versions of argocd-helm, argocd-operator to ArgoCD version 3 (#304)
* upgrade versions of argocd-helm, argocd-operator to ArgoCD version 3
* add information about ingress to developer.md
---------
Co-authored-by: Thomas Michael <thomas.michael@cloudogu.com>
make deploy IMG=quay.io/argoprojlabs/argocd-operator:v0.14.1
978
+
make deploy IMG=quay.io/argoprojlabs/argocd-operator:v0.15.0
972
979
```
973
980
974
-
### Steps in depth
981
+
### Install ingress manually
975
982
976
-
1. Clone the repository from GitHub and switch to the release-0.11 branch.
977
-
2. Apply a patch that disables the Cert-Manager webhooks by commenting out certain sections in the kustomization.yaml file in the default configuration. The ArgoCD Operator fails at startup if this webhook is not disabled and no cert-manager is present in the cluster.
978
-
3. The patch also changes the image tag in the kustomization.yaml file located in the manager directory from version v0.11.1 to v0.11.0. The Version v0.11.1 does not exist in the Repository anymore, but is referenced in the Kustomization.
979
-
4. Install the Prometheus CRDs. These Custom Resource Definitions are necessary for monitoring the operator and will prevent a successful startup if not present.
980
-
5. Install the ArgoCD Operator CRDs and components using kubectl kustomize.
983
+
The ArgoCD installed via Operator is namespace isolated and therefor can not deploy an ingress-controller, because of global scoped configurations.
984
+
GOP has to be startet with ``` --insecure ``` because of we do not use https locally.
985
+
We have to install the ingress-controller manually:
0 commit comments