Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitbf17a42

Browse files
authored
Gitops helm install (#652)
* Add topic for helm hybrid gitops install* Update hybrid-gitops-helm-installation.md* Update hybrid-gitops-helm-installation.md* Update nav.ymlAdded helm install for hybrid gitops* Update nav.yml* Update hybrid-gitops-helm-installation.md* Update hybrid-gitops-helm-installation.md* Update hybrid-gitops-helm-installation.md* Update hybrid-gitops-helm-installation.mdAdded latest changes with ingress flags for ingress-based runtimes* Update hybrid-gitops-helm-installation.md* Update hybrid-gitops-helm-installation.md* Update hybrid-gitops-helm-installation.md* Update hybrid-gitops-helm-installation.mdFixed nested lists indentation* Update hybrid-gitops-helm-installation.md* Update hybrid-gitops-helm-installation.mdAdded --devel flag install command and --helm update command to create Helm repo command* Update hybrid-gitops-helm-installation.md* Update hybrid-gitops-helm-installation.md* Update hybrid-gitops-helm-installation.md* Update hybrid-gitops-helm-installation.md* Update hybrid-gitops-helm-installation.mdAdded double quotes to global.runtime.ingress.hosts[0] and added ingress configuration steps at end of install proc* Update hybrid-gitops-helm-installation.md* Update hybrid-gitops-helm-installation.mdFixed links to post-install ingress configuration* Update hybrid-gitops-helm-installation.md* Update hybrid-gitops-helm-installation.md* Update hybrid-gitops-helm-installation.mdFixed line breaks and list numbering* Update hybrid-gitops-helm-installation.md* Update hybrid-gitops-helm-installation.md* Update hybrid-gitops-helm-installation.md* Update hybrid-gitops-helm-installation.md* Update hybrid-gitops-helm-installation.md* Update hybrid-gitops-helm-installation.mdRemoved commented out step* Update hybrid-gitops-helm-installation.mdContent updates* Update monitor-manage-runtimes.mdUpdated Upgrade task content* Update hybrid-gitops-helm-installation.md* Update* Update Helm runtime install and manage topics* Update monitor-manage-runtimes.mdFixed heading levels* Update monitor-manage-runtimes.mdCommented out Download logs and Restore runtime procs until further notice from Dev* Update hybrid-gitops-helm-installation.mdAdded redirect from previous hybrid install topic* Update content for install and manage runtimesAdded CLI options for config repo and git credentials updates* Add new icons fro topology view* Update hybrid-gitops-helm-installation.md* Update content for Helm runtimes* Update uninstallReplaced "upgrade" with "Uninstall"* Updated topology view iconsReplaced existing icons in topology view table* Update runtime-topology-add-cluster.png* Add image for missing shared repo* Update monitor-manage-runtimes.mdAdded Helm chart version to Version description for List view* Update content* Update shared-configuration.mdEdited content to reflect new Helm-based install* Update reset ISC for helmContent edits for ISC; added CLI command to rest ISC* Update upgrade for Helm gitops runtimesEdited upgrade topic with instructions for gitops managed runtimes* Add image override utility and update reset ISCAdded bullet item on image override utility in Helm install and updated procedure to reset ISC* Update helm validationUpdated Helm validation step to indicate automated validation* Update hybrid helm runtimeReordered and streamlined content acc to feedback from Kostis* Remove legacy hybrid runtime from toc* Update quick install sectionAdded post-install note for git providers and ISC for quick install* Add beta tag to Hybrid GitOps* Add image override blurb
1 parent796be15 commitbf17a42

File tree

29 files changed

+1216
-306
lines changed

29 files changed

+1216
-306
lines changed

‎_data/home-content.yml‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -231,9 +231,9 @@
231231
-title:On-Premises upgrade
232232
localurl:/docs/installation/codefresh-on-prem-upgrade/
233233
-title:Hosted GitOps installation
234-
localurl:/docs/installation/gitops/hosted-runtime/
235-
-title:Hybrid GitOps installation
236-
localurl:/docs/installation/gitops/hybrid-gitops/
234+
localurl:/docs/installation/gitops/hosted-runtime/
235+
-title:Hybrid GitOpsHelminstallation
236+
localurl:/docs/installation/gitops/hybrid-gitops-helm-installation/
237237

238238

239239

‎_data/nav.yml‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -502,9 +502,9 @@
502502
url:
503503
sub-pages:
504504
-title:Hosted GitOps Runtime
505-
url:"/hosted-runtime"
506-
-title:Hybrid GitOps Runtime
507-
url:"/hybrid-gitops"
505+
url:"/hosted-runtime"
506+
-title:Hybrid GitOpsHelmRuntime
507+
url:"/hybrid-gitops-helm-installation"
508508
-title:Managing & monitoring GitOps Runtimes
509509
url:"/monitor-manage-runtimes"
510510
-title:Add external clusters to GitOps Runtimes

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

Lines changed: 935 additions & 82 deletions
Large diffs are not rendered by default.

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

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,19 @@ title: "Hybrid GitOps Runtime installation"
33
description:"Provision Hybrid GitOps Runtimes"
44
group:installation
55
sub_group:gitops
6+
redirect_from:
7+
-/csdp-docs/docs/runtime/installation/
8+
-/csdp-docs/docs/runtime/requirements/
69
toc:true
710
---
811

12+
>ATTENTION:
13+
>We have transitioned to a Helm-based installation for Hybrid GitOps Runtimes, for improved experience and performance.
14+
15+
>The CLI-based installation for Hybrid GitOps is now considered legacy. We will deprecate this installation mode permanently on 18 June 2023.
16+
>To migrate your Hybrid GitOps Runtimes from CLI to Helm, please contact us, and we'll migrate them for you.
17+
18+
919
Provision one or more Hybrid GitOps Runtimes in your Codefresh account.
1020
Start by reviewing[system requirements](#minimum-system-requirements) for Hybrid GitOps.
1121
If you are installing with ingress-controllers, you must configure them as required_before_ starting the installation.

‎_docs/installation/gitops/monitor-manage-runtimes.md‎

Lines changed: 250 additions & 203 deletions
Large diffs are not rendered by default.

‎_docs/reference/shared-configuration.md‎

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,26 +1,25 @@
11
---
2-
title:"Sharedconfiguration repo"
3-
description:""
2+
title:"SharedConfiguration Repository"
3+
description:"Share configuration settings across GitOps Runtimes"
44
group:reference
55
toc:true
66
---
77

88

9-
A Codefresh account with a Hosted or a Hybrid GitOps runtime can store configuration manifests for account-level resources in a Git repository. This repository can be shared with other runtimes in the same account, avoiding the need to create and maintain different configuration manifests for everyruntime.
9+
A Codefresh account with a Hosted or a Hybrid GitOps runtime can store configuration manifests for account-level resources in a Git repository. This repository can be shared with other runtimes in the same account, avoiding the need to create and maintain different configuration manifests for everyGitOps Runtime.
1010

11-
* Hosted GitOpsruntimes
12-
As part of the setup for a Hosted GitOps runtime, Codefresh creates theshared configuration repository in the selected organization, together with the default Git Source repo. See[Connect Git provider]({{site.baseurl}}/docs/installation/gitops/hosted-runtime/#2-connect-git-provider) in Hosted GitOps setup.
11+
* Hosted GitOpsRuntimes
12+
As part of the setup for a Hosted GitOps runtime, Codefresh creates theShared Configuration Repository in the selected organization, together with the default Git Source repo. See[Connect Git provider]({{site.baseurl}}/docs/installation/gitops/hosted-runtime/#2-connect-git-provider) in Hosted GitOps setup.
1313

14-
* Hybridruntimes
15-
When you install the firsthybridruntime for an account, youcan manually define the shared configuration repo through the`--shared-config-repo` flag. Or, you can allow Codefreshtoautomatically createtheshared configuration repo in the runtime installation repo, in`shared-config` root.See[Installinghybrid runtimes]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops/#install-hybrid-gitops-runtime).
14+
* HybridGitOps Runtimes
15+
When you install the firstHybrid GitOpsruntime for an account, youare requiredtodefinetheShared Configuration Repo as part of setting up your Git account.See[InstallingHybrid GitOps Helm Runtime installation]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/#step-3-set-up-gitops-git-account).
1616

17-
For older versions of hybrid runtimes, upgrade the runtime to create the shared configuration repo, as described in[Upgrading hybrid runtimes](#upgrading-hybrid-runtimes) later in this article.
1817

19-
>Currently, Codefresh supports a singleshared configuration repo per account.
20-
Youcan alsoreset theshared configuration repo if needed. See[Reset shared configuration repository for GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/monitor-manage-runtimes/#reset-shared-configuration-repository-for-gitops-runtimes).
18+
>Currently, Codefresh supports a singleShared Configuration Repo per account.
19+
Youmay need toreset theShared Configuration Repo after creating it. See[Reset shared configuration repository for GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/monitor-manage-runtimes/#reset-shared-configuration-repository-for-gitops-runtimes).
2120

2221

23-
##Sharedconfiguration repo structure
22+
##SharedConfiguration Repo structure
2423
Below is a representation of the structure of the repository with the shared configuration.
2524
See a[sample repo](https://github.dev/noam-codefresh/shared-gs){:target="\_blank"}.
2625

@@ -97,14 +96,15 @@ spec:
9796
9897
9998
## Git Source application per runtime
100-
In addition to the application manifests forthe runtimes in the shared configuration repository, everyruntime has a Git Source application that references`runtimes/<runtime-name>`.
99+
In addition to the application manifests forGitOps Runtimes in the shared configuration repository, everyGitOps Runtime has a Git Source application that references`runtimes/<runtime-name>`.
101100

102-
This Git Source application creates an application manifest with the `<cluster-name>` for every cluster managed by theruntime. The `include` field in the `<cluster-name>` application manifest determines which subdirectories in the `resources` directory are synced to the target cluster.
101+
This Git Source application creates an application manifest with the `<cluster-name>` for every cluster managed by theGitOps Runtime. The `include` field in the `<cluster-name>` application manifest determines which subdirectories in the `resources` directory are synced to the target cluster.
103102

104103

105104
## Adding resources
106-
When creating a new resource, such as a new integration for example in the Codefresh UI, you can define theruntimes and clusters to which to apply that resource. The app-proxy saves the resource in the correct location and updates the relevant Argo CD Applications to include it.
105+
When creating a new resource, such as a new integration for example in the Codefresh UI, you can define theGitOps Runtimes and clusters to which to apply that resource. The app-proxy saves the resource in the correct location and updates the relevant Argo CD Applications to include it.
107106

107+
<!--
108108
## Upgrading hybrid runtimes
109109
Older hybrid runtimes that do not have the shared configuration repository must be upgraded to the latest version.
110110
You have two options to define the shared configuration repository during upgrade:
@@ -115,7 +115,7 @@ You have two options to define the shared configuration repository during upgrad
115115

116116
If the hybrid runtime being upgraded has managed clusters, once the shared configuration repo is created for the account either automatically or manually on upgrade, all clusters are migrated to the same repo when app-proxy is initialized. An Argoproj application manifest is committed to the repo for each cluster managed by the runtime.
117117

118-
See [(Hybrid) Upgrade provisioned runtimes]({{site.baseurl}}/docs/installation/gitops/monitor-manage-runtimes/#hybrid-gitops-upgrade-provisioned-runtimes).
118+
See [(Hybrid) Upgrade provisioned runtimes]({{site.baseurl}}/docs/installation/gitops/monitor-manage-runtimes/#hybrid-gitops-upgrade-provisioned-runtimes). -->
119119

120120

121121

-6.17 KB
Binary file not shown.
-6.19 KB
Binary file not shown.
-6.17 KB
Binary file not shown.
-6.24 KB
Binary file not shown.

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp