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

Commit4ea6d89

Browse files
committed
Update codefresh-runner.md
1 parent26f787a commit4ea6d89

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

‎_docs/administration/codefresh-runner.md‎

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ As the Codefresh Runner is **not** dependent on any special dockershim features,
2929
##Codefresh Runner installation
3030
Install the Runner from any workstation or laptop with access to the Kubernetes cluster running Codefresh builds, via`kubectl`. The Codefresh Runner authenticates to your Codefresh account using the CLI token.
3131

32-
>**Notes:**
32+
>**Notes:**
3333
You_must_ install the Codefresh Runner on_every cluster that runs Codefresh pipelines_.
3434
The Runner is**not** needed in clusters used for_deployment_, as you can deploy applications on clusters without the Runner.
3535
<br />
@@ -181,7 +181,7 @@ codefresh runner execute-test-pipeline --runtime-name <runtime-name>
181181

182182
### Complete Codefresh Runner installation
183183

184-
If the Kubernetes cluster with the Codefresh Runner is behind a proxy server without direct access to`g.codefresh.io`,there areadditional steps tocomplete theCodefresh Runnerinstallation process.
184+
If the Kubernetes cluster with the Codefresh Runner is behind a proxy server without direct access to`g.codefresh.io`,follow theadditional steps tocomplete the installation.
185185

186186
**Before you begin**
187187
Make sure you have [installed the Codefresh Runner](#codefresh-runner-installation) using any of the options
@@ -541,13 +541,12 @@ Now any container image used in your pipeline and isn't fully qualified, will be
541541
542542
### Add custom labels to dind and engine pods
543543
Add custom labels to your Engine and Dind pods in Runtime Environment (RE) by patching it.
544-
544+
{:start="1"}
545545
1. Get the configuration of the RE and place it in a file named`runtime.yaml`.
546546
`codefresh get runtime-environments -o yaml<$RUNTIME_ENVIRONMENT>> runtime.yaml`
547547
where:
548548
`$RUNTIME_ENVIRONMENT` must be replaced with the name of your RE.
549-
1. Edit the`dockerDaemonScheduler.labels` or`runtimeScheduler.labels` property of`runtime.yaml` to include the label, as in the example below.
550-
>If the`dockerDaemonScheduler.labels` are not included in the RE configuration by default, add them.
549+
1. Edit the`dockerDaemonScheduler.labels` or`runtimeScheduler.labels` property of`runtime.yaml` to include the label, as in the example below. If the`dockerDaemonScheduler.labels` are not included in the RE configuration by default, add them.
551550
```yaml
552551
version: 1
553552
metadata:
@@ -570,7 +569,7 @@ dockerDaemonScheduler:
570569
where:
571570
`$RUNTIME_ENVIRONMENT` must be replaced with the name of your RE.
572571
573-
Once you have applied the patch, future builds include the label preventing eviction.
572+
Once you have applied the patch, future buildswillinclude the label preventing eviction.
574573
575574
576575
## View Codefresh Runner and runtime environments

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp