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
*`<codefresh-account-id>` is mandatory only for _tunnel-based Hybrid GitOps Runtimes_ , which is also the default access mode. Automatically populated by Codefresh in the installation command.
378
378
*`<codefresh-api-key>` is the API key, either an existing one or a new API key you generated. When generated, it is automatically populated in the command.
379
379
*`<runtime-name>` is the name of the GitOps Runtime, and is either `codefresh` which is the default, or the custom name you define.
380
-
*`<helm-repo-name>` is the name of the repo in which to store the Helm chart, and must be identical to the `<helm-repo-name>` you defined in _step 3_, either `cf-gitops-runtime` which is the default, or any custom name you define.
381
380
*`gitops-runtime` is the chart name defined by Codefresh, and cannot be changed.
382
381
* GitOps with Argo CD installation:
383
382
*`argo-cd.fullnameOverride=codefresh-argo-cd` is mandatory when _installing GitOps with Argo CD_ to avoid conflicts at the cluster-level for resources in both the Community Argo CD and GitOps Runtime's Argo CD.
@@ -598,8 +597,6 @@ The Git provider and Shared Configuration Repository is configured once per acco
598
597
**Shared Configuration Repository and Git provider**
599
598
The Shared Configuration Repository and Git provider are configured once per account, and not required for additional installations.
600
599
601
-
**Helm chart repository**
602
-
The repository for the Helm chart is also configured per account, and is not required for additional installations in the same account.
603
600
604
601
**Access mode**
605
602
You can define the tunnel/ingress/service-mesh-based access mode for the additional GitOps Runtimes you install. The command in the How To below is valid for the tunnel-based access mode. For ingress-based or service-mesh-based access modes, add the required arguments and values, as described in the step-by-step section, [Step 3: Install Hybrid GitOps Runtime](#step-3-install-hybrid-gitops-runtime).
0 commit comments