|
| 1 | +--- |
| 2 | +title: "Side-by-side: Argo CD and GitOps Runtimes" |
| 3 | +description: "Install GitOps Runtimes with Argo CD" |
| 4 | +group: installation |
| 5 | +toc: true |
| 6 | +--- |
| 7 | + |
| 8 | + |
| 9 | +## Prepare for side-by-side |
| 10 | + |
| 11 | +Same minor version for Argo CD & Codefresh GitOps |
| 12 | +Argo CD must have the same minor version as Codefresh GitOps. |
| 13 | + |
| 14 | +When installing Argo CD using Helm, we recommend using the same upstream chart version as Codefresh. |
| 15 | +Where is this?? You can find this version in the dependencies for the [gitops-runtime chart](https://github.com/codefresh-io/gitops-runtime-helm/blob/main/charts/gitops-runtime/Chart.yaml). |
| 16 | +The version will look like this: <upstream chart version>-<codefresh-version id> |
| 17 | + |
| 18 | +CRD adoption |
| 19 | +When installing GitOps with the native Argo CD, we recommned that the Custom Resource Definitionsby managed by the GitOps Runtime's Helm release. Doing so ensures that when you upgrade the Hybrid GitOps Runtime, the CRDs are also automatically upgraded. |
| 20 | +You can adopt all CRDs or only |
| 21 | + |
| 22 | +This also applies to Argo Rollout CRDs, as there should only be one active Argo Rollouts controller in the cluster and . To adopt only CRDs for rollouts, run the following script (only if you haven't executed the script to adopt all CRDs mentioned above). Make sure to set your release name and namespace: |
| 23 | +Run this script before installation: |
| 24 | + |
| 25 | +Resource collisions |
| 26 | +To prevent collisions with Argo CD and Argo Rollouts resources on the cluster, set `fullnameOverride` arguments in the Helm with the custom values. |
| 27 | +* For Argo CD: |
| 28 | +``` |
| 29 | +argo-cd: |
| 30 | + fullnameOverride: codefresh-argo-cd |
| 31 | +``` |
| 32 | +* For Argo Rollouts: |
| 33 | +``` |
| 34 | +argo-rollouts: |
| 35 | + fullnameOverride: codefresh-argo-rollouts |
| 36 | +``` |
| 37 | +In the context of your snippet, codefresh-argo-cd is used as the custom value for fullnameOverride. This means that when Helm installs the "argo-cd" chart, it will use codefresh-argo-cd as the base name for Kubernetes resources, rather than the default release name provided during the Helm installation. |
| 38 | + |
| 39 | +Annotations for resource tracking |
| 40 | +If ArgoCD and gitops-runtime ArgoCD use the same resource tracking method, collisions can occur when using the same application names or tracking the same resource from both ArgoCDs. |
| 41 | +GitOps Runtimes use annotations to track resources. For side-by-side installation, this means that native Argo CD's resource tracking method is not set, which means it defaults to `label` or must be explicty set as `label`. |
| 42 | + |
| 43 | + |
| 44 | + |
| 45 | +## Installation |
| 46 | + |
| 47 | + |
| 48 | +## Post installation |
| 49 | + |
| 50 | + |
| 51 | + |
| 52 | +## |
| 53 | + |
0 commit comments