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

Commitfe6b862

Browse files
authored
Update monitor-manage-runtimes.md (#831)
* Update monitor-manage-runtimes.md* Update monitor-manage-runtimes.mdCommented out download log description in table
1 parent6168549 commitfe6b862

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

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

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ Here is a description of the information in the List View.
8787
|**Version**| The version of the Runtime currently installed (CLI installations), including the version of the Helm chart (Helm installations) .**Update Available!** indicates there are newer versions of the Runtime or Helm chart. To see all the commits, mouse over**Update Available!**, and select**View Complete Change Log**.
8888
|**Last Updated**| The most recent update information from the runtime to the Codefresh platform. Updates are sent to the platform typically every few minutes. Longer update intervals may indicate networking issues.|
8989
|**Sync Status**| The sync status of the GitOps Runtime. The sync status is displayed only when you have completed installation and configured the GitOps Runtime as an Argo Application. {::nomarkdown}<ul><li> <imgsrc="../../../../images/icons/runtime-synced.png"display=inline-block> <b>Synced</b></li> <li><imgsrc="../../../../images/icons/runtime-syncing.png"display=inline-block> <b>Syncing</b>.</li><li><imgsrc="../../../../images/icons/runtime-out-of-sync.png"display=inline-block> <b>Out-of-sync</b>.</li><li><b>N/A</b>: Codefresh could not get the sync status. This could be because the Runtime is not configured as an Argo application.</li><li><b>Complete Installation</b>: Git credentials are not configured for the Runtime. Click the three-dot context menu and select <b>Update Git Runtime Credentials</b>. See[Update Git credentials for GitOps Runtimes](#update-git-credentials-for-gitops-runtimes).</li> </ul> {:/}|
90-
|**Actions** | The possible actions to manage the selected runtime.{::nomarkdown}<ul><li> <b>Upgrade</b>: Upgrade to the latest version. See <a href="https://codefresh.io/docs/docs/installation/gitops/monitor-manage-runtimes/#upgrade-gitops-runtimes">Upgrade GitOps Runtimes</a></li> <li><b>Download All Logs</b>: Valid only for _legacy_ Hybrid GitOps Runtimes.<br>Download logs for the Runtime or for its components. See <a href="https://codefresh.io/docs/docs/installation/gitops/monitor-manage-runtimes/#viewdownload-logs-to-troubleshoot-gitops-runtimes">View/download logs for GitOps Runtimes</a></li><li><b>Update Git Runtime Credentials</b>: Update Git token for Runtime. See </li><li><b>Remove Runtime</b>: Available only when the runtime is Offline. <br>Remove the runtime from Codefresh. The runtime remains on the cluster. See <a href="https://codefresh.io/docs/docs/installation/gitops/monitor-manage-runtimes/#remove-gitops-runtimes">Remove GitOps Runtimes</a>. </li><li><b>Uninstall Runtime</b>: Uninstall the runtime from the cluster on which it is provisioned. See <a href="https://codefresh.io/docs/docs/installation/gitops/monitor-manage-runtimes/#uninstall-gitops-runtimes">Uninstall GitOps Runtimes</a></li> </ul> {:/}
90+
|**Actions** | The possible actions to manage the selected runtime.{::nomarkdown}<ul><li> <b>Upgrade</b>: Upgrade to the latest version. See <a href="https://codefresh.io/docs/docs/installation/gitops/monitor-manage-runtimes/#upgrade-gitops-runtimes">Upgrade GitOps Runtimes</a></li> <!--- <li><b>Download All Logs</b>: Valid only for _legacy_ Hybrid GitOps Runtimes.<br>Download logs for the Runtime or for its components. See <a href="https://codefresh.io/docs/docs/installation/gitops/monitor-manage-runtimes/#viewdownload-logs-to-troubleshoot-gitops-runtimes">View/download logs for GitOps Runtimes</a></li>--><li><b>Update Git Runtime Credentials</b>: Update Git token for Runtime. See </li><li><b>Remove Runtime</b>: Available only when the runtime is Offline. <br>Remove the runtime from Codefresh. The runtime remains on the cluster. See <a href="https://codefresh.io/docs/docs/installation/gitops/monitor-manage-runtimes/#remove-gitops-runtimes">Remove GitOps Runtimes</a>. </li><li><b>Uninstall Runtime</b>: Uninstall the runtime from the cluster on which it is provisioned. See <a href="https://codefresh.io/docs/docs/installation/gitops/monitor-manage-runtimes/#uninstall-gitops-runtimes">Uninstall GitOps Runtimes</a></li> </ul> {:/}
9191

9292

9393
###Topology view
@@ -526,7 +526,9 @@ Uninstalling a GitOps Runtime permanently removes:
526526

527527

528528
## (Helm GitOps) Download logs for GitOps Runtimes
529+
Download logs for the GitOps Runtime from the Kubernetes cluster.
529530

531+
<!---
530532
Download the logs for a completed GitOps Runtime installation.<br>
531533
The Runtime log is downloaded as a `.tar.gz` file, which contains the individual log files for each runtime component.
532534

@@ -633,7 +635,7 @@ Online logs show up to 1000 of the most recent events (lines), updated in real t
633635
The file is downloaded as `<component-name>.log`.
634636

635637

636-
638+
-->
637639

638640

639641
## (Legacy CLI Hybrid GitOps) Restoring provisioned GitOps Runtimes

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp