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-on-prem.md
+7-22Lines changed: 7 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,13 +88,16 @@ Edit the configuration in `config.yaml` and deploy to Kubernetes. The `config.ya
88
88
89
89
####Installation Methods (Helm)
90
90
91
-
You have the option to install by using Helm, which will install/upgrade the chart from the client.
92
-
Defineeither**helm** as your preferred installation method in the`config.yaml`:
91
+
You have the option to install by using**Helm**, which will install/upgrade the chart from the client.
92
+
Define**helm** as your preferred installation method in the`config.yaml`:
93
93
94
94
```yaml
95
+
metadata:
95
96
installer:
96
-
# type:
97
-
# "helm" - install/upgrade helm chart from client
97
+
type:helm
98
+
helm:
99
+
chart:codefresh
100
+
repoUrl:https://chartmuseum.codefresh.io/codefresh# install/upgrade helm chart from client
98
101
```
99
102
100
103
If you install Codefresh on the air-gapped environment (without access to public Docker Hub or codefresh-enterprise registry) you will have to copy the images to your organization container registry (Kubernetes will pull the images from it as part of the installation).
@@ -143,24 +146,6 @@ Deploy the Codefresh Platform by running:
### 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
-
164
149
165
150
## High-Availability (HA) with active-passive clusters
166
151
Enable high-availability in the Codefresh platform for disaster recovery with an active-passive cluster configuration.