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

Commit246a58a

Browse files
committed
Update monitor-manage-runtimes.md
1 parentce8e825 commit246a58a

File tree

1 file changed

+33
-1
lines changed

1 file changed

+33
-1
lines changed

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

Lines changed: 33 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -159,7 +159,7 @@ If you have managed clusters for Hybrid GitOps Runtimes, upgrading the Runtime a
159159
1. For GitOps Runtimes, do the following:
160160
1. In your Shared Configuration Repository, go to`resources/<runtime_name>/chart`
161161
where,`<runtime_name>` is the name of the Hybrid GitOps Runtime to upgrade.
162-
1. Inthe`chart.yaml`, change the version number in both`.version` and`.dependencies.version`.
162+
1. In`chart.yaml`, change the version number in both`.version` and`.dependencies.version`.
163163
1. Commit the change, and push to your Git server.
164164
```yaml
165165
apiVersion:v2
@@ -202,6 +202,38 @@ Changelogs for all versions, including historical versions are available on GitH
202202

203203
* [Changelogs for GitOps Runtimes](https://github.com/codefresh-io/gitops-runtime-helm/releases){:target="\_blank"}
204204

205+
## Rollback GitOps Runtimes
206+
Rollback to a previous version after upgrading a GitOps Runtime.
207+
208+
The rollback procedure differs slightly depending on whether the GitOps Runtime has been configured as an Argo CD application or not.
209+
210+
##### Argo CD GitOps Runtimes
211+
Manually change the version in the Helm chart (`chart.yaml`) located in the Shared Configuration Repository.
212+
213+
1. In your Shared Configuration Repository, go to `resources/<runtime_name>/chart`
214+
where:
215+
`<runtime_name>`is the name of the Hybrid GitOps Runtime to upgrade.
216+
1. In `chart.yaml`, change the version number in both `.version` and `.dependencies.version`.
217+
1. Commit the change, and push to your Git server.
218+
219+
##### Non-Argo CD GitOps Runtimes
220+
Use Helm commands such as `rollback` (rollback to a specfic version) or `upgrade` (upgrade to a specific previous version).
221+
222+
* `helm rollback`
223+
Example:
224+
`helm rollback <runtime_name> <rollback-version>`
225+
where:
226+
* `<runtime_name>` is the name of the Hybrid GitOps Runtime to roll back to.
227+
* `<rollback-version>` is the version of the GitOps Runtime to roll back to.
228+
229+
* `helm upgrade`
230+
Example:
231+
`helm upgrade <runtime_name> --version <rollback-version>`
232+
where:
233+
* `<runtime_name>` is the name of the Hybrid GitOps Runtime to roll back to.
234+
* `<rollback-version>` is the version of the GitOps Runtime to roll back to.
235+
236+
205237

206238
## Update Git credentials for GitOps Runtimes
207239

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp