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/administration/codefresh-runner.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1647,27 +1647,27 @@ You can [monitor the runner](#using-the-codefresh-runner).
1647
1647
1648
1648
### Install monitoring component
1649
1649
1650
-
If your cluster is located [behind the firewall]({{site.baseurl}}/docs/administration/behind-the-firewall/), youmay want to use the Runner's monitoring component to get valuable information about cluster resources to Codefresh dashboards. For example, to [Kubernetes](https://g.codefresh.io/kubernetes/services/){:target="\_blank"} and [Helm Releases](https://g.codefresh.io/helm/releases/releasesNew/){:target="\_blank"} dashboards.
1650
+
If your cluster is located [behind the firewall]({{site.baseurl}}/docs/administration/behind-the-firewall/), youcan use the Runner's monitoring component to get valuable information about cluster resources to Codefresh dashboards. For example, to [Kubernetes](https://g.codefresh.io/kubernetes/services/){:target="\_blank"} and [Helm Releases](https://g.codefresh.io/helm/releases/releasesNew/){:target="\_blank"} dashboards.
1651
1651
1652
1652
You can install the monitoring component during Runner installation with cluster integration, or after Runner installation without cluster integration.
* `<CONTEXT>`, `<NAMESPACE>`,'<CLUSTER_NAME>' are the context, namespace, and the name of the cluster to which install the monitoring component.
1661
-
* `<TOKEN>` is the token to authenticate to the cluster.
1660
+
* `--install-monitor` is by default set to `true` and installs the monitoring component that makes valuable data on the cluster available to Codefresh.
If you defined the `--skip-cluster-integration` flag to skip cluster integration during Runner installation, then you cannot install the monitoring component during the installation.
1665
-
To get cluster resource information to the Codefresh dashboards in this case, install the monitoring component separately after completing the Runner installation.
1663
+
If you defined the `--skip-cluster-integration` flag to skip cluster integration during Runner installation, then you cannot install the monitoring component during the installation. Install the monitoring component separately after completing the Runner installation to get cluster resource information to the Codefresh dashboards.