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
= Configuring ingress control in {microshift-short}
9
9
10
-
You can use detailed ingress control settings by updating the {microshift-short} service configuration file.
10
+
You can use detailed ingress control settings by updating the {microshift-short} service configuration file or using a configuration snippet.
11
+
12
+
[IMPORTANT]
13
+
====
14
+
* A `config.yaml` configuration file takes precedence over built-in settings. The `config.yaml` file is read every time the {microshift-short} service starts.
15
+
* Configuration snippet YAMLs take precedence over both built-in settings and the `config.yaml` configuration file.
16
+
====
11
17
12
18
.Prerequisites
13
19
@@ -20,18 +26,8 @@ You can use detailed ingress control settings by updating the {microshift-short}
20
26
. Apply ingress control settings in one of the two following ways:
21
27
22
28
.. Update the {microshift-short} `config.yaml` configuration file by making a copy of the provided `config.yaml.default` file in the `/etc/microshift/` directory, naming it `config.yaml` and keeping it in the source directory.
23
-
+
24
-
[IMPORTANT]
25
-
====
26
-
After you create the `config.yaml`, the configuration file takes precedence over built-in settings. The `config.yaml` file is read every time the {microshift-short} service starts.
27
-
====
28
29
29
30
.. Use a configuration snippet to apply the ingress control settings you want. To do this, create a configuration snippet YAML file and put it in the `/etc/microshift/config.d/` configuration directory.
30
-
+
31
-
[IMPORTANT]
32
-
====
33
-
Configuration snippet YAMLs take precedence over both built-in settings and the `config.yaml` configuration file.
34
-
====
35
31
36
32
. Replace the default values in the `ingress` section of the {microshift-short} YAML with your valid values, or create a configuration snippet file with the sections you need.
37
33
+
@@ -235,7 +231,7 @@ When configured, this field must contain a valid expression or the {microshift-s
235
231
====
236
232
237
233
|`clientTLS.clientCA`
238
-
|Specifies a required config map that is in the `openshift-ingress` namespace. Required to enable client TLS. The config map must contain a certificate authority (CA) bundle.
234
+
|Specifies a required config map that is in the `openshift-ingress` namespace. Required to enable client TLS. The config map must contain a certificate authority (CA) bundle named `ca-bundle.pem` or the deployment of the default router fails.
239
235
240
236
|`clientTLS.clientCA.name`
241
237
|The `metadata.name` of the config map referenced in the `clientTLS.clientCA` value.
0 commit comments