Skip to content

Commit 1c5777a

Browse files
authored
Update argo project components req (#746)
* Update argo project components req Added that cluster cannot include argo project components * Update hybrid-gitops-helm-installation.md * Update hybrid-gitops-helm-installation.md
1 parent dbda3c3 commit 1c5777a

File tree

1 file changed

+10
-7
lines changed

1 file changed

+10
-7
lines changed

_docs/installation/gitops/hybrid-gitops-helm-installation.md

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -25,15 +25,15 @@ For step-by-step installation from the Codefresh UI, see [Step-by-step Hybrid Gi
2525

2626
Install the Hybrid GitOps Runtime via Helm with the default tunnel-based access mode. You will copy the Helm install command from the UI to get the values that Codefresh automatically retrieves for you such as your account ID and other values.
2727

28-
The Codefresh `values.yaml` is located [here](https://github.com/codefresh-io/gitops-runtime-helm/blob/main/charts/gitops-runtime/){:target="\_blank"}.
28+
The Codefresh `values.yaml` is located [here](https://github.com/codefresh-io/gitops-runtime-helm/blob/main/charts/gitops-runtime/){:target="\_blank"}. It contains all the arguments that can be configured, including optional ones.
2929

3030
### Before running quick install
3131

3232
**Notes & assumptions**
3333
Quick installation assumes that:
3434
* You have set up a Git provider and the Shared Configuration Repository for your account. If these are not defined, you can define them _after_ installation from the Codefresh UI, when prompted to do so.
3535
See [Update Git credentials for GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/monitor-manage-runtimes/#update-git-credentials-for-gitops-runtimes) and [Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration/)
36-
* Your cluster does not have [Argo project CRDs](#argo-project-crds).
36+
* Your cluster does not have [Argo project components & CRDs](#argo-project-components--crds).
3737

3838

3939
**Automated validation**
@@ -76,8 +76,11 @@ where:
7676

7777

7878

79-
## Argo project CRDs
80-
Hybrid GitOps installation requires a cluster without Argo project CRDs.
79+
## Argo project components & CRDs
80+
Hybrid GitOps installation requires a cluster without Argo project components and CRDs.
81+
82+
Argo project components include Argo Rollouts, Argo CD, Argo Events, and Argo Workflows.
83+
8184
You can handle Argo project CRDs outside the chart, or as recommended, adopt the CRDs to be managed by the GitOps Runtime Helm release.
8285

8386
If you already have Argo project CRDs on your cluster, do one of the following:
@@ -173,15 +176,15 @@ global:
173176
## Step-by-step Hybrid GitOps Runtime installation
174177
Install the Hybrid GitOps Runtime via Helm from the Codefresh UI.
175178

176-
The Codefresh `values.yaml` is located [here](https://github.com/codefresh-io/gitops-runtime-helm/tree/main/charts/gitops-runtime){:target="\_blank"}.
179+
The Codefresh `values.yaml` is located [here](https://github.com/codefresh-io/gitops-runtime-helm/blob/main/charts/gitops-runtime/){:target="\_blank"}. It contains all the arguments that can be configured, including optional ones.
177180

178181
### Before you begin
179182
* Make sure you meet the [minimum requirements](#minimum-system-requirements) for installation
180183
* Git provider requirements:
181184
* [Runtime token with the required scopes]({{site.baseurl}}/docs/reference/git-tokens/#git-runtime-token-scopes). You need to supply as part of the Helm install command.
182185
* [Personal Access Token (PAT)]({{site.baseurl}}/docs/reference/git-tokens/#git-personal-tokens) with the required scopes for Git-based actions.
183186
* Server URLs for on-premises Git providers
184-
* Verify there are no Argo project CRDs in the target namespace or that you have adopted the CRDs (see [Argo project CRDs](#argo-project-crds))
187+
* Verify there are no Argo project components and CRDs in the target namespace or that you have adopted the CRDs (see [Argo project components & CRDs](#argo-project-components--crds))
185188
* For ingress-based runtimes only, verify that these ingress controllers are configured correctly:
186189
* [Ambassador ingress configuration](#ambassador-ingress-configuration)
187190
* [AWS ALB ingress configuration](#aws-alb-ingress-configuration)
@@ -463,7 +466,7 @@ You can now add [external clusters to the Runtime]({{site.baseurl}}/docs/install
463466
{: .table .table-bordered .table-hover}
464467
| Item | Requirement |
465468
| -------------- | -------------- |
466-
|Kubernetes cluster | Server version 1.18 and higher, without Argo Project components. {::nomarkdown}<br><b>Tip</b>: To check the server version, run:<br> <code class="highlighter-rouge">kubectl version --short</code>.{:/}|
469+
|Kubernetes cluster | Server version 1.18 and higher, _without_ Argo Project components. {::nomarkdown}<br><b>Tip</b>: To check the server version, run:<br> <code class="highlighter-rouge">kubectl version --short</code>.{:/}|
467470
|Node requirements| {::nomarkdown}<ul><li>Memory: 5000 MB</li><li>CPU: 2</li></ul>{:/}|
468471
|Cluster permissions | Cluster admin permissions |
469472
|Git providers |{::nomarkdown}<ul><li>GitHub</li><li>GitHub Enterprise</li><li>GitLab Cloud</li><li>GitLab Server</li><li>Bitbucket Cloud</li><li>Bitbucket Server</li></ul>{:/}|

0 commit comments

Comments
 (0)