Skip to content

Commit c0b0bf1

Browse files
NimRegevNimRegev
committed
Update hybrid-gitops-helm-installation.md
1 parent d3fd8eb commit c0b0bf1

File tree

1 file changed

+15
-13
lines changed

1 file changed

+15
-13
lines changed

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

Lines changed: 15 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ Choose the installation option that best aligns with your specific requirements
3333
* **First-time GitOps Runtime installation**
3434
If this is your first time installing a GitOps Runtime in your Codefresh account, follow these steps:
3535

36-
* [Complete pre-requisites](#prepare-for-gitops-runtime-installation): Before starting the installation, complete pre-requisites, as described in Prepare for GitOps Runtime Installation.
36+
* [Complete pre-requisites](#preparing-for-hybrid-gitops-runtime-installation): Before starting the installation, complete pre-requisites, as described in Prepare for GitOps Runtime Installation.
3737
* [System requirements](#minimum-system-requirements): Check the minimum system requirements to ensure smooth installation.
3838
* [Step-by-step installation](#install-first-gitops-runtime-in-account): Follow our step-by-step guide to install the Hybrid GitOps Runtime from the Codefresh UI.
3939

@@ -53,22 +53,27 @@ Terminology clarifications:
5353
In the documentation, Hybrid GitOps Runtimes are also referred to as GitOps Runtimes.
5454

5555

56-
## Preparing for Hybrid GitOps installation
56+
## Preparing for Hybrid GitOps Runtime installation
5757

5858

59-
Whether you are installing GitOps on a clean cluster without Argo CD or on a cluster with Argo CD, you have to complete the prerequisites for a smooth installation.
59+
Whether you are installing GitOps Runtimes on a clean cluster without Argo CD or on a cluster with Argo CD, you have to complete the prerequisites for a smooth installation.
6060

6161

6262
| Prerequisite | GitOps only | GitOps with Argo CD |
6363
|------------------------------------- |:------------: |:-------------: |
64-
| [Argo Project components](#gitops-only-argo-project-components) | ✅ | N/A |
65-
| [Argo Project CRDs(Custom Resource Definitions)](#gitops-onlygitops-with-argo-cd-argo-project-crds) | ✅ | ✅ |
66-
| [Argo Rollout CRDs(Custom Resource Definitions)](#gitops-onlygitops-with-argo-cd-argo-rollout-crds) | ✅ | ✅ |
67-
| [Synchronize Argo CD chart's minor versions](#gitops-with-argo-cd-synchronize-argo-cd-charts-minor-versions) | N/A | ✅ |
68-
| [Set native Argo CD resource tracking to `label](#gitops-with-argo-cd-set-native-argo-cd-resource-tracking-to-label) | N/A | ✅ |
64+
|[Argo Project components](#gitops-only-argo-project-components) | ✅ | N/A |
65+
|[SealedSecrets controller](#gitops-only-sealedsecrets-controller) | ✅ | N/A |
66+
|[Argo Project CRDs(Custom Resource Definitions)](#gitops-onlygitops-with-argo-cd-argo-project-crds) | ✅ | ✅ |
67+
|[Argo Rollout CRDs(Custom Resource Definitions)](#gitops-onlygitops-with-argo-cd-argo-rollout-crds) | ✅ | ✅ |
68+
|[Synchronize Argo CD chart's minor versions](#gitops-with-argo-cd-synchronize-argo-cd-charts-minor-versions) | N/A | ✅ |
69+
|[Set native Argo CD resource tracking to `label](#gitops-with-argo-cd-set-native-argo-cd-resource-tracking-to-label) | N/A | ✅ |
6970

7071
### GitOps only: Argo Project components
71-
When installing a GitOps Runtime on a cluster with Standalone GitOps, the GitOps Runtime cluster must not have any Argo Project components: Argo Rollouts, Argo CD, Argo Events, and Argo Workflows.
72+
When installing only the GitOps Runtime on the cluster, the cluster should not have any Argo Project components: Argo Rollouts, Argo CD, Argo Events, and Argo Workflows.
73+
74+
### GitOps only: SealedSecrets controller
75+
When installing only the GitOps Runtime on the cluster, the cluster should not have SealedSecret controller components.
76+
7277

7378
### GitOps only/GitOps with Argo CD: Argo Project CRDs
7479
If you already have Argo Project CRDs on your cluster, Codefresh recommends adopting the CRDs to switch ownership for them to the GitOps Runtime, or handling the CRDs outside the chart.
@@ -172,14 +177,11 @@ The Codefresh `values.yaml` located [here](https://github.com/codefresh-io/gitop
172177

173178
### Before you begin
174179
* Make sure you meet the [minimum requirements](#minimum-system-requirements) for installation
180+
* Verify that you complete all the [prerequisites](#preparing-for-hybrid-gitops-runtime-installation) as required
175181
* Git provider requirements:
176182
* [Git Runtime token with the required scopes]({{site.baseurl}}/docs/reference/git-tokens/#git-runtime-token-scopes) which you need to supply as part of the Helm install command
177183
<!--- * [Git user token]({{site.baseurl}}/docs/reference/git-tokens/#git-personal-tokens) with the required scopes for Git-based actions -->
178184
* Server URLs for on-premises Git providers
179-
* For GitOps installation with Argo CD, verify the following:
180-
* [Minor version of Argo CD's Helm chart](#side-by-side-gitops-minor-versions) is identical to the version used by Codefresh
181-
* [Native Argo CD's resource tracking is set to `label`](#side-by-side-gitops-set-native-argo-cd-resource-tracking-to-label)
182-
* Verify there are no Argo Project CRDs in the target namespace or that you have adopted the CRDs (see [Argo Project components & CRDs](#argo-project-components--crds))
183185
* For ingress-based runtimes only, verify that these ingress controllers are configured correctly:
184186
* [Ambassador ingress configuration](#ambassador-ingress-configuration)
185187
* [AWS ALB ingress configuration](#aws-alb-ingress-configuration)

0 commit comments

Comments
 (0)