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

Commit486b7a9

Browse files
committed
Update codefresh-runner.md
Edited Runner monitoring component installation
1 parent250fb07 commit486b7a9

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

‎_docs/administration/codefresh-runner.md‎

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1647,25 +1647,26 @@ You can [monitor the runner](#using-the-codefresh-runner).
16471647
16481648
### Install monitoring component
16491649
1650-
If your cluster is located [behind the firewall]({{site.baseurl}}/docs/administration/behind-the-firewall/) youmight want to use the Runner monitoring component to get valuable information aboutthecluster resourcesinto Codefresh,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/), 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.
16511651
1652-
You can install the monitoring component withor without cluster integration.
1652+
You can install the monitoring componentduring Runner installationwithcluster integration, or after Runner installation without cluster integration.
16531653
1654-
#### Install _with_ cluster integration
1654+
#### Install _with_ cluster integration _during_ Runner install
1655+
The cluster integration is created automatically during Runner installation.
16551656
```shell
16561657
codefresh install monitor --kube-context-name <CONTEXT> --kube-namespace <NAMESPACE> --cluster-id <CLUSTER_NAME> --token <TOKEN>
16571658
```
16581659
where:
16591660
* `<CONTEXT>`, `<NAMESPACE>`,'<CLUSTER_NAME>' are the context, namespace, and the name of the cluster to which install the monitoring component.
16601661
* `<TOKEN>` is the token to authenticate to the cluster.
16611662
1662-
#### Install _without_ cluster integration
1663+
#### Install _without_ cluster integration _after_ Runner install
1664+
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.
16631666
16641667
```shell
1665-
codefreshrunner init --install-monitor --skip-cluster-integrationtrue
1668+
codefreshinstall monitor --kube-context-name <CONTEXT> --kube-namespace <NAMESPACE> --cluster-id <CLUSTER_NAME> --token <TOKEN>
16661669
```
1667-
where:
1668-
`--skip-cluster-integration` is optional, and whenset to`true` does not create a cluster integration.
16691670
16701671
16711672
### Injecting AWS ARN roles into the cluster

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp