Skip to content

Commit beb246a

Browse files
authored
Update hybrid-gitops-helm-installation.md (#1047)
* Update hybrid-gitops-helm-installation.md * Update hybrid-gitops-helm-installation.md Added CLI command for ingress disable and changed value to true
1 parent 15109cc commit beb246a

File tree

1 file changed

+24
-5
lines changed

1 file changed

+24
-5
lines changed

_docs/installation/gitops/hybrid-gitops-helm-installation.md

Lines changed: 24 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -132,7 +132,7 @@ kubectl annotate --overwrite crds $(kubectl get crd | grep argoproj.io | awk '{p
132132
Before initiating the installation, Codefresh automatically validates the `values.yaml` file to verify that the supplied values are correct.
133133
A validation error will automatically terminate the installation.
134134

135-
You can disable automated validation and manually run the validation if desired.
135+
You can also disable automated validation globally for all installation settings or for only the ingress controller, and run validation manually.
136136

137137
### Validated settings
138138
The table below lists the settings validated in the `values` file.
@@ -155,7 +155,7 @@ To get more detailed and meaningful information on the reason for the validation
155155
where:
156156
* `{NAMESPACE}` must be replaced with the namespace of the Hybrid GitOps Runtime.
157157

158-
### Disable automated validation
158+
### Disable global installation validation
159159
You may want to disable automated validation for specific scenarios, such as to address false-negatives.
160160
Do so by either adding the flag to the Helm install command or adding the relevant section to the values file.
161161

@@ -172,6 +172,28 @@ installer: skipValidation: true
172172
{% endraw %}
173173
{% endhighlight %}
174174

175+
### Disable ingress validation
176+
Ingress validation checks if the ingress URL exists and responds to web requests.
177+
During a GitOps Runtime installation, the ingress might not be active yet, causing DNS errors despite correct configuration. Disabling ingress validation allows the installation to proceed, assuming the ingress will work once the Runtime is fully operational.
178+
179+
Similar to disabling installation validation globally, you disable the validation for ingress by either adding the flag to the Helm install command or adding the relevant section to the values file.
180+
181+
##### In install command
182+
183+
`--set global.runtime.ingress.skipValidation=true`
184+
185+
##### In values file
186+
187+
{% highlight yaml %}
188+
{% raw %}
189+
...
190+
global:
191+
runtime:
192+
ingress:
193+
skipValidation: true
194+
...
195+
{% endraw %}
196+
{% endhighlight %}
175197

176198
### Manually validate values.yaml
177199
To manually validate the values file, run:
@@ -188,9 +210,6 @@ If this is the first GitOps Runtime installation in your Codefresh account, inst
188210
The Codefresh `values.yaml` located [here](https://github.com/codefresh-io/gitops-runtime-helm/blob/main/charts/gitops-runtime/){:target="\_blank"}, contains all the arguments you can configure, including optional ones. See ???
189211

190212

191-
192-
193-
194213
### Before you begin
195214
* Make sure you meet the [minimum requirements](#minimum-system-requirements) for installation
196215
* Verify that you complete all the prerequisites:

0 commit comments

Comments
 (0)