Skip to content

Commit 6b88516

Browse files
NimRegevNimRegev
authored
Q2 s3 side by side install (#836)
* Create argo-with-gitops-side-by-side.md * Add content for side-by-side install Added prereqs and updated step-by-step for side-by-side * Update hybrid-gitops-helm-installation.md Content updates * Update helm runtime with side-by-side Added first version of side-by-side options * Update hybrid-gitops-helm-installation.md Added terminology clarifications, more content edits for additional installations * Add side-by-side-article Added article for Gitops with Argo CD with xrefs to config and install section in hybrid install * Update side-by-side and helm install topics * Update hybrid-gitops-helm-installation.md * Update hybrid-gitops-helm-installation.md Updated additional runtime install section with new widget guided install * Update hybrid-gitops-helm-installation.md * Add complete install widget screenshot * Add screenshots Added screenshots to main procedure * Add missing screenshots Updated additional runtime install and added missing screenshots * Update migrate argo cd application Updated content and added screenshots for migrating argo cd apps * Update hybrid install Content and screenshot edits * Update Git provider and ISC step Updated content for Git provider and ISC to align with the new design and added screenshots * Update side-by-side content Updated minor version sync content acc to Ilia's feedback * Update hybrid-gitops-helm-installation.md Separated Rollouts issues * Update behind-the-firewall.md * Update behind-the-firewall.md * Update hybrid-gitops-helm-installation.md * Update hybrid-gitops-helm-installation.md * Update argo-with-gitops-side-by-side.md * Update hybrid-gitops-helm-installation.md * Update hybrid-gitops-helm-installation.md * Update argo-with-gitops-side-by-side.md * Update argo-with-gitops-side-by-side.md * Update hybrid-gitops-helm-installation.md * Update content Updated with feedback from Franscisco; replaced "native" Argo CD with "community" * Fix formatting and terminology Updated formatting; title of side-by-side * Update hybrid-gitops-helm-installation.md
1 parent 5384461 commit 6b88516

File tree

3 files changed

+210
-189
lines changed

3 files changed

+210
-189
lines changed

‎_data/nav.yml

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@
2222
- title: CI/CD quick starts
2323
url: "/ci-quick-start"
2424
sub-pages:
25-
- title: Pipeline quick starts
25+
- title: Pipeline quick start
2626
url: "/create-ci-pipeline"
2727
- title: Kubernetes deployment quick start
2828
url: "/deploy-to-kubernetes"
@@ -39,11 +39,11 @@
3939
url: "/verify-requirements"
4040
- title: Install a Hybrid GitOps Runtime
4141
url: "/runtime"
42-
- title: Create `codefresh-guestbook` Argo CD application
42+
- title: Create an application
4343
url: "/create-app-ui"
44-
- title: Create & commit resources for `codefresh-guestbook` application
44+
- title: Create and commit resources for application
4545
url: "/create-app-specs"
46-
- title: Update image tag for `codefresh-guestbook` application
46+
- title: Update the image tag for application
4747
url: "/create-rollout"
4848

4949
- title: Dashboards & insights
@@ -351,17 +351,17 @@
351351
- title: GitOps
352352
url: "/gitops"
353353
sub-pages:
354-
- title: Creating Argo CD applications
354+
- title: Creating GitOps applications
355355
url: "/create-application"
356-
- title: Monitoring Argo CD applications
356+
- title: Monitoring GitOps applications
357357
url: "/applications-dashboard"
358-
- title: Managing Argo CD applications
359-
url: "/manage-application"
360-
- title: Application Groups for Argo CD applications
358+
- title: Application Groups for GitOps applications
361359
url: "/gitops-app-groups"
360+
- title: Managing GitOps applications
361+
url: "/manage-application"
362362
- title: Progressive delivery with GitOps
363363
url: "/install-argo-rollouts"
364-
- title: Troubleshooting Argo CD applications
364+
- title: Troubleshooting GitOps applications
365365
url: "/troubleshooting-gitops-apps"
366366

367367
- title: Pipelines
@@ -508,7 +508,7 @@
508508
url: "/hosted-runtime"
509509
- title: Hybrid GitOps Runtime
510510
url: "/hybrid-gitops-helm-installation"
511-
- title: Hybrid GitOps Runtime with existing Argo CD
511+
- title: Hybrid GitOps Runtime alongside Community Argo CD
512512
url: "/argo-with-gitops-side-by-side"
513513
- title: On-premises GitOps Runtime
514514
url: "/on-prem-gitops-runtime-install"

‎_docs/installation/gitops/argo-with-gitops-side-by-side.md

Lines changed: 14 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Install GitOps Runtime alongside existing Argo CD"
2+
title: "Install GitOps Runtime alongside Community Argo CD"
33
description: "Install GitOps Runtime on cluster with existing Argo CD"
44
group: installation
55
toc: true
@@ -16,7 +16,8 @@ If you have a cluster with Argo CD already installed, Codefresh provides an opti
1616

1717
For a smooth transition from Argo CD Applications to Codefresh's GitOps applications, migrate Applications at your preferred pace. On successful migration, view, track, and manage all aspects of the applications in Codefresh.
1818

19-
19+
<br>
20+
2021
Follow these steps to install the GitOps Runtime on a cluster with Argo CD:
2122
* Prepare the Argo CD cluster for GitOps Runtime installation
2223
* Install the GitOps Runtime via Helm
@@ -26,9 +27,11 @@ Follow these steps to install the GitOps Runtime on a cluster with Argo CD:
2627
## Prepare Argo CD cluster for GitOps Runtime installation
2728

2829
There are three configuration changes to make _before_ installing the GitOps Runtime on the cluster with Argo CD:
29-
1. [Switch ownership of Argo project CRDs]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/#gitops-onlygitops-with-argo-cd-argo-project-crds)
30-
2. [Synchronize Argo CD chart's minor versions]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/#gitops-with-argo-cd-synchronize-argo-cd-charts-minor-versions)
31-
3. [Set native Argo CD resource tracking to `label`]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/#gitops-with-argo-cd-set-native-argo-cd-resource-tracking-to-label)
30+
31+
1. [Switch ownership of Argo project CRDs]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/#gitops-runtime-onlygitops-runtime-with-argo-cd-argo-project-crds)
32+
2. [Align Argo CD chart's minor versions]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/#gitops-runtime-with-argo-cd-synchronize-argo-cd-charts-minor-versions)
33+
3. [Set Community Argo CD resource tracking to `label`]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/#gitops-runtime-with-argo-cd-set-community-argo-cd-resource-tracking-to-label)
34+
3235

3336

3437
## Install Hybrid GitOps Runtime via Helm
@@ -38,8 +41,9 @@ After completing the configuration changes, follow our [step-by-step installatio
3841
The GitOps Runtime installation is Helm-based, and installing the Runtime on a cluster with an existing Argo CD, requires additional flags in the installation command and an additional step after installation.
3942

4043

41-
## Migrate Argo CD Applications to Codefresh GitOps Runtime
42-
The final task depending on your requirements is to migrate your Argo CD Applications to the Codefresh GitOps Runtime.
44+
45+
## Migrate Community Argo CD Applications to Codefresh GitOps Runtime
46+
The final task depending on your requirements is to migrate your Community Argo CD Applications to the Codefresh GitOps Runtime.
4347

4448
Why would you want to do this?
4549
Because this allows you to completely and seamlessly manage the applications in Codefresh as GitOps entities.
@@ -106,9 +110,9 @@ spec:
106110
107111
108112
109-
### Step 3: Commit the application to the Git Source
110-
As the final step in migrating your Argo CD Application to a Codefresh GitOps one, manually commit the updated Application manifest to the Git Source you created in Step 1.
111-
Once you commit the manifest to the Git Source, it is converted into a GitOps application. You can view it in the Codefresh UI, modify definitions, track it through our different dashboards, and in short, manage it as you would any GitOps resource in Codefresh.
113+
### Step 3: Commit Argo CD application to Git Source
114+
As the final step in migrating your Argo CD Application to a Codefresh GitOps Runtime, manually commit the updated application manifest to the Git Source you created in Step 1.
115+
Once you commit the manifest to the Git Source, it is synced with the Git repo. You can view it in the Codefresh UI, modify definitions, track it through our different dashboards, and in short, manage it as you would any GitOps resource in Codefresh.
112116
113117
1. Go to the Git repo where you created the Git Source.
114118
1. Add and commit the Argo CD Application manifest to the Git Source.

0 commit comments

Comments
 (0)