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

Commit1b1b620

Browse files
upd onprem doc
1 parent2730637 commit1b1b620

File tree

1 file changed

+0
-18
lines changed

1 file changed

+0
-18
lines changed

‎_docs/administration/codefresh-on-prem.md‎

Lines changed: 0 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -143,24 +143,6 @@ Deploy the Codefresh Platform by running:
143143
```
144144
kcfi deploy [ -c config.yaml ] [ --kube-context <kube-context-name> ] [ --atomic ] [ --debug ] [ helm upgrade parameters ]
145145
```
146-
### Step 5 -- Install the Codefresh Kubernetes Agent
147-
148-
The cf-k8s-agent is responsible for accessing Kubernetes resources (pods, deployments, services, etc.) behind the firewall in order to display them in the Codefresh UI. It can be installed in a separate cluster from the installer, or in a separate namespace in the same cluster.
149-
150-
The agent streams updates from cluster resources and then sends information updates to the `k8s-monitor` service.
151-
152-
Execute the following:
153-
154-
```
155-
kcfi init k8s-agent
156-
```
157-
A staging directory will be created named k8s-agent with a `config.yaml`.
158-
Edit k8s-agent/config.yaml and run:
159-
160-
```
161-
kcfi deploy [ -c config.yaml ] [-n namespace]
162-
```
163-
164146

165147
## High-Availability (HA) with active-passive clusters
166148
Enable high-availability in the Codefresh platform for disaster recovery with an active-passive cluster configuration.

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp