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

Commit17bbe09

Browse files
committed
Update monitor-manage-runtimes.md
1 parent910e1fa commit17bbe09

File tree

1 file changed

+24
-21
lines changed

1 file changed

+24
-21
lines changed

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

Lines changed: 24 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -123,8 +123,8 @@ If you have managed clusters for Hybrid GitOps Runtimes, upgrading the Runtime a
123123
#####How to
124124
1. In the Codefresh UI, on the toolbar, click the**Settings** icon.
125125
1. From Runtimes in the sidebar, select[**GitOps Runtimes**](https://g.codefresh.io/2.0/account-settings/runtimes){:target="\_blank"}, and then switch to either**List View** or to the**Topology View**.
126-
1. To upgrade in**List view**, move to the**Version** column and do the following:
127-
1. To see the changes in the new version of the Runtime, mouse over**Update Available!**, andselect**View Complete Change Log**.
126+
1. To upgrade in**List view**, move to the**Version** column, and do the following:
127+
1. To see the changes in the new version of the Runtime, mouse over**Update Available!**, andclick**View Complete Change Log**.
128128
1. Do one of the following:
129129
* To the right of the row with the Runtime to upgrade, click the context menu and select**Upgrade**.
130130
* Click the Runtime name, and then click**Upgrade** on the top-right.
@@ -154,11 +154,12 @@ If you have managed clusters for Hybrid GitOps Runtimes, upgrading the Runtime a
154154

155155
{:start="5"}
156156
1. Do one of the following depending on whether you have configured the Runtime as an Argo CD Application or not:
157-
* Argo CD GitOps Runtimes: Continue fromstep_6_.
158-
* Non-Argo CD GitOps Runtimes: Continue fromstep_7_.
157+
* Argo CD GitOps Runtimes: Continue from_step 6_.
158+
* Non-Argo CD GitOps Runtimes: Continue from_step 7_.
159159
1. For GitOps Runtimes, do the following:
160-
1. In your Shared Configuration Repository, go to`resources/<runtime_name>/chart`
161-
where,`<runtime_name>` is the name of the Hybrid GitOps Runtime to upgrade.
160+
1. In your Shared Configuration Repository, go to`resources/<runtime_name>/chart`
161+
where:
162+
`<runtime_name>` is the name of the Hybrid GitOps Runtime to upgrade.
162163
1. In`chart.yaml`, change the version number in both`.version` and`.dependencies.version`.
163164
1. Commit the change, and push to your Git server.
164165
```yaml
@@ -178,55 +179,57 @@ dependencies:
178179
1. To exit the upgrade panel, click **Close**.
179180

180181
## (Hybrid GitOps) View changelogs for GitOps Runtimes
181-
Each version of a GitOps Runtime includes a changelog detailing the changes in that release.
182+
Each version of a GitOps Runtime includes a changelog detailing the changes in that release.
182183

183-
#####Upgrade notification & changelog for latest Runtime release
184+
#####Changelog for latest Runtime release
184185
In the GitOps Runtimes List view, the Version column displays the current version installed.
185186

186187
Whenever there is a newer version of the Runtime, Helm chart, or both, the **Update Available!** notification appears in the same column.
187-
Mouse over shows a link to the changelog for that version on GitHub, labeled as **Latest**, as in the example below.
188+
Mouse over shows a link to the changelog for that version on GitHub.
189+
The example below shows the changelog for the **Latest** release of the GitOps Runtime.
188190

189191
{% include
190192
image.html
191193
lightbox="true"
192194
file="/images/runtime/helm/runtime-changelog.png"
193195
url="/images/runtime/helm/runtime-changelog.png"
194-
alt="Changelogfor GitOpsRuntimes on GitHub"
195-
caption="Changelogfor GitOpsRuntimes on GitHub"
196+
alt="Example of changelogfor GitOpsRuntime on GitHub"
197+
caption="Example of changelogfor GitOpsRuntime on GitHub"
196198
max-width="60%"
197199
%}
198200

199201

200-
#####Changelog for all Runtime releases
201-
Changelogs for all versions, including historical versions are available on GitHub.
202+
#####Changelogs for all Runtime releases
203+
Changelogs for all versions, including historical versions, are available on GitHub.
202204

203-
*[Changelogs for GitOps Runtimes](https://github.com/codefresh-io/gitops-runtime-helm/releases){:target="\_blank"}
205+
*Go to [GitHub](https://github.com/codefresh-io/gitops-runtime-helm/releases){:target="\_blank"} to see changelogs for all GitOps Runtime versions.
204206

205-
## (Hybrid GitOps)Rollback GitOps Runtimes
206-
After upgrading a GitOps Runtime,rollbacktoa previous or a specific version of the Runtime.
207+
## (Hybrid GitOps)Roll back GitOps Runtimes
208+
After upgrading a GitOps Runtime,roll backtothe previous or a specific version of the Runtime.
207209

208210
The rollback procedure differs slightly depending on whether the GitOps Runtime has been configured as an Argo CD application or not.
209211

210212
##### Argo CD GitOps Runtimes
211213
Manually change the version in the Helm chart (`chart.yaml`) located in the Shared Configuration Repository.
212214

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.
215+
1. In your Shared Configuration Repository, go to:
216+
`resources/<runtime_name>/chart`
217+
where:
218+
`<runtime_name>`is the name of the Hybrid GitOps Runtime to upgrade.
216219
1. In `chart.yaml`, change the version number in both `.version` and `.dependencies.version`.
217220
1. Commit the change, and push to your Git server.
218221

219222
##### Non-Argo CD GitOps Runtimes
220223
Use Helm commands such as `rollback` or `upgrade`.
221224

222-
* `helm rollback`
225+
* `helm rollback`
223226
Example:
224227
`helm rollback <runtime_name> <rollback-version>`
225228
where:
226229
* `<runtime_name>` is the name of the Hybrid GitOps Runtime to roll back to.
227230
* `<rollback-version>` is the version of the GitOps Runtime to roll back to.
228231

229-
* `helm upgrade`
232+
* `helm upgrade`
230233
Example:
231234
`helm upgrade <runtime_name> --version <rollback-version>`
232235
where:

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp