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

Commit75290bf

Browse files
upd
1 parenteb9c753 commit75290bf

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

‎_docs/administration/codefresh-runner.md‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -111,8 +111,6 @@ codefresh runner init --dry-run
111111

112112
This will execute the wizard in a special mode that will not actually install anything in your cluster. After all configuration questions are asked, all Kubernetes manifests used by the installer will be instead saved locally in a folder`./codefresh_manifests`.
113113

114-
You can then inspect the manifests locally or edit/apply them manually if you wish.
115-
116114
##Installing Codefresh Runner with values file
117115

118116
To install the Codefresh Runner with pre-defined values file use`--values` flag:
@@ -152,7 +150,7 @@ To install the Codefresh Runner using Helm, follow these steps:
152150
```
153151
>**Note!**<br />
154152
Runtime components' (engine and dind) configuration is determined by the `runner init` command. <br />
155-
The `helm install` command can only control the configuration of `runner`, `dind-volume-provisioner` and `lv-monitor` components
153+
The `helm install` command can only control the configuration of `runner`, `dind-volume-provisioner` and `lv-monitor` components.
156154
157155
## Using the Codefresh Runner
158156

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp