You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _docs/installation/gitops/managed-cluster.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,13 +26,14 @@ Optionally, to first generate the YAML manifests, and then manually apply them,
26
26
* For_Hosted GitOps_ Runtimes:[Configure access to these IP addresses]({{site.baseurl}}/docs/administration/platform-ip-addresses/)
27
27
* Verify that:
28
28
* Your Git personal access token is valid and has the[required scopes]({{site.baseurl}}/docs/reference/git-tokens)
29
-
* You haveinstalledthe[latest version of the Codefresh CLI]({{site.baseurl}}/docs/clients/#upgrade-gitops-cli)
29
+
* You have the[latest version of the Codefresh CLI]({{site.baseurl}}/docs/installation/gitops/upgrade-gitops-cli/)
30
30
31
31
**How to**
32
32
33
-
1. In the Codefresh UI, on the toolbar, click the**Settings** icon, expand Runtimes in the sidebar, and select[**GitOps Runtimes**](https://g.codefresh.io/2.0/account-settings/runtimes){:target="\_blank"}.
33
+
1. In the Codefresh UI, on the toolbar, click the**Settings** icon.
34
+
1. From Runtimes in the sidebar, select[**GitOps Runtimes**](https://g.codefresh.io/2.0/account-settings/runtimes){:target="\_blank"}.
34
35
1. From either the**Topology** or**List** views, select the Runtime to which to add the cluster.
Copy file name to clipboardExpand all lines: _docs/installation/gitops/monitor-manage-runtimes.md
+12-8Lines changed: 12 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -238,9 +238,10 @@ Pass the mandatory flags in the uninstall command:
238
238
239
239
**GitOps CLI wizard uninstall**
240
240
241
-
1. In the Codefresh UI, on the toolbar, click the**Settings** icon, expand Runtimes in the sidebar, and select[**GitOps Runtimes**](https://g.codefresh.io/2.0/account-settings/runtimes){:target="\_blank"}.
241
+
1. In the Codefresh UI, on the toolbar, click the**Settings** icon.
242
+
1. From Runtimes in the sidebar, select[**GitOps Runtimes**](https://g.codefresh.io/2.0/account-settings/runtimes){:target="\_blank"}.
242
243
1. Switch to either the**List View** or to the**Topology View**.
243
-
1.**List view**:On thetop-right, select the three dots and then select**Uninstall**.
244
+
1.**List view**:To the right of the runtime to delete, select the three dots and then select**Uninstall**.
244
245
245
246
{% include
246
247
image.html
@@ -291,8 +292,8 @@ Provisioned Runtimes require valid Git tokens at all times to authenticate Git a
291
292
>These tokens are specific to the user, and the same can be used for multiple runtimes.
292
293
293
294
There are two different situations when you need to update Git tokens:
294
-
*Update invalid, revoked, or expired tokens: Codefresh automatically flags Runtimes with such tokens. It is mandatory to update the Git tokens to continue working with the platform.
295
-
*Update valid tokens: Optional. You may want to update Git tokens, even valid ones, by deleting the existing token and replacing it with a new token.
295
+
*Invalid, revoked, or expired tokens: Codefresh automatically flags Runtimes with such tokens. It is mandatory to update the Git tokens to continue working with the platform.
296
+
*Valid tokens: Optional. You may want to update Git tokens, even valid ones, by deleting the existing token and replacing it with a new token.
296
297
297
298
The methods for updating any Git token are the same regardless of the reason for the update:
298
299
* OAuth2 authorization, if your admin has registered an OAuth Application for Codefresh
@@ -307,7 +308,7 @@ The methods for updating any Git token are the same regardless of the reason for
307
308
The GitOps Runtimes page shows runtimes with invalid tokens prefixed by the key icon. Mouse over shows invalid token.
308
309
* To update an existing token, go to[GitOps Runtimes](https://g.codefresh.io/2.0/account-settings/runtimes){:target="\_blank"}.
309
310
1. Select the GitOps Runtime for which to update the Git token.
310
-
1. From the context menuwith the additional actionsat thetop-right, select**Update Git Runtimetoken**.
311
+
1. From the context menu at the right, select**Update Git RuntimeCredentials**.
311
312
312
313
{% include
313
314
image.html
@@ -432,8 +433,8 @@ Online logs show up to 1000 of the most recent events (lines), updated in real t
@@ -557,6 +558,7 @@ All you need to do is to configure the browser to trust the URL and receive cont
557
558
558
559
1. Select **View Runtimes** to the right of the alert.
559
560
You are taken to the Runtimes page, where you can see insecure Runtimes tagged as **Allow Insecure**.
561
+
<!--- ask dev for help -->
560
562
{% include
561
563
image.html
562
564
lightbox="true"
@@ -581,6 +583,8 @@ The Activity Log is a quick way to monitor notifications for Runtime events such
581
583
1. In the Codefresh UI, on the top-right of the toolbar, select  **Activity Log**.
582
584
1. To see notifications for provisioned Runtimes, filter by **Runtime**.
583
585
586
+
587
+
<!--- ask dev for help -->
584
588
{% include image.html
585
589
lightbox="true"
586
590
file="/images/runtime/runtime-activity-log.png"
@@ -606,7 +610,7 @@ Runtimes with sync errors display an **Out of sync** status in Sync Status colum
606
610
**View errors**
607
611
For both views, select the Runtime, and then select **Errors Detected**.
608
612
Here is an example of health errors for a Runtime.