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
* Fix numbering in platform certs proc* Update hybrid-gitops-helm-installation.mdFixed broken links* Add updates for validation stepUpdated content for validation step with debug and disable options* Update validation and install stepsImplemented review comments for validation step;added yaml formatting for install commands and fixed note on populated values
Unless otherwise indicated, values are automatically populated by Codefresh.
34
+
If you're using a terminal, remember to copy the values from the UI beforehand.<br>
35
+
32
36
where:
33
37
*`<helm-release-name>` is the name of the Helm release.
34
38
*`<namespace>` is the namespace in which to install the Hybrid GitOps runtime, either`codefresh`, or the custom name you defined.
35
-
*`<codefresh-account-id>` is your Codefresh account ID.
36
39
*`<codefresh-api-key>` is the generated API key.
37
40
*`<runtime-name>` is the name of the runtime, either`codefresh`, or the custom name you defined.
38
41
*`gitops-runtime` is the chart name defined by Codefresh.
@@ -107,7 +110,9 @@ The Codefresh `values.yaml` is located [here](https://github.com/codefresh-io/gi
107
110
Codefresh automatically validates the`values.yaml` file before initiating the installation to verify that the supplied values are correct.
108
111
You also have the option to manually run the validation if desired.
109
112
110
-
<!--- **Validation failure**
113
+
114
+
**Validation failure**
115
+
111
116
If there is a validation failure, Codefresh will terminate the Helm installation and display the error message:`Job has reached the specified backoff limit`.
112
117
113
118
To get more detailed and meaningful information on the reason for the validation failure, run:
@@ -135,7 +140,8 @@ installer:
135
140
{% endraw %}
136
141
{% endhighlight %}
137
142
138
-
**Validated settings**-->
143
+
144
+
**Validated settings**
139
145
140
146
The table below lists the settings validated in the`values` file.
141
147
@@ -157,11 +163,7 @@ The table below lists the settings validated in the `values` file.
157
163
where:
158
164
*`<values_file>` is the name of the values.yaml used by the Helm installation.
159
165
*`<namespace>` is the namespace in which to install the Hybrid GitOps runtime, either the default`codefresh`, or the custom name you intend to use for the installation. The Namespace must conform to the naming conventions for Kubernetes objects.
160
-
*`<version>` is the version of the runtime to install.
161
-
<!---1. If there is a validation failure, to see more details on the reasons for the failure, run:
>Unless otherwise indicated, values are automatically populated by Codefresh.
258
+
where:
259
+
*
260
+
* `<helm-release-name>` is the name of the Helm release.
261
+
* `<namespace>` is the namespace in which to install the Hybrid GitOps runtime, either `codefresh`, or the custom name you defined.
262
+
* `<codefresh-account-id>` is mandatory only for _tunnel-based Hybrid GitOps Runtimes_.
263
+
* `<codefresh-api-key>` is the generated API key.
264
+
* `<runtime-name>` is the name of the runtime, either `codefresh`, or the custom name you defined.
265
+
* `gitops-runtime` is the chart name defined by Codefresh.
266
+
* `global.runtime.ingress.enabled=true` is mandatory for _ingress-based Hybrid GitOps Runtimes_, and indicates that the runtime is ingress-based.
267
+
* `<ingress-host>` is mandatory for _ingress-based Hybrid GitOps Runtimes_, and is the IP address or host name of the ingress controller component.
268
+
* `<ingress-class>` is mandatory for _ingress-based Hybrid GitOps Runtimes_, and is the ingress class of the ingress controller. For example, `nginx` for the NGINX ingress controller.
269
+
* `--wait` waits until all the pods are up and running for the deployment.
228
270
229
-
where:
230
-
* `<helm-release-name>` is the name of the Helm release.
231
-
* `<namespace>` is the namespace in which to install the Hybrid GitOps runtime, either `codefresh`, or the custom name you defined.
232
-
* `<codefresh-account-id>` is your Codefresh account ID.
233
-
* `<codefresh-api-key>` is the generated API key.
234
-
* `<runtime-name>` is the name of the runtime, either `codefresh`, or the custom name you defined.
235
-
* `gitops-runtime` is the chart name defined by Codefresh.
236
-
* `global.runtime.ingress.enabled=true` is mandatory for _ingress-based Hybrid GitOps Runtimes_, and indicates that the runtime is ingress-based.
237
-
* `<ingress-host>` is mandatory for _ingress-based Hybrid GitOps Runtimes_, and is the IP address or host name of the ingress controller component.
238
-
* `<ingress-class>` is mandatory for _ingress-based Hybrid GitOps Runtimes_, and is the ingress class of the ingress controller. For example, `nginx` for the NGINX ingress controller.
239
-
* `--wait` waits until all the pods are up and running for the deployment.
271
+
{:start="5"}
240
272
1. Wait for a few minutes, and then click**Close**.
241
273
You are taken to the List View for GitOps Runtimes where you can see the Hybrid GitOps Runtime you added prefixed with a red dot.
242
274
1. Continue with[Step 5: Configure Git credentials for runtime](#step-5-configure-git-credentials-for-hybrid-gitops-runtime).