@@ -163,6 +163,28 @@ under the key ``data.config\.yaml``:
163
163
metalk8s-ingress-controller-config
164
164
165
165
166
+ The following documentation is not exhaustive and is just here to give
167
+ some hints on basic usage, for more details or advanced
168
+ configuration, see the official `Nginx Ingress Controller documentation `_.
169
+
170
+ .. _Nginx Ingress Controller documentation : https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/
171
+
172
+ Control plane Ingress Controller Configuration Customization
173
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
174
+
175
+ Same as the Workload plane Ingress Controller, Control Plane can be overridden
176
+ by editing its Cluster and Service ConfigMap
177
+ ``metalk8s-ingress-control-plane-controller-config ``
178
+ in namespace ``metalk8s-ingress ``
179
+ under the key ``data.config\.yaml ``:
180
+
181
+ .. code-block :: shell
182
+
183
+ root@bootstrap $ kubectl --kubeconfig /etc/kubernetes/admin.conf \
184
+ edit configmap -n metalk8s-ingress \
185
+ metalk8s-ingress-control-plane-controller-config
186
+
187
+
166
188
The following documentation is not exhaustive and is just here to give
167
189
some hints on basic usage, for more details or advanced
168
190
configuration, see the official `Nginx Ingress Controller documentation `_.
@@ -186,6 +208,29 @@ HTTP2 can be disabled by setting ``use-http2`` to ``false``:
186
208
config:
187
209
use-http2: "false"
188
210
211
+ Modify authorized Ciphers
212
+ """""""""""""""""""""""""
213
+
214
+ Strong cipher configurations may not allow legacy user agents or user agents
215
+ with weak configurations to connect to your site. If your server must also
216
+ pass to a legacy upstream server, this may prevent it from being able to
217
+ negotiate a cipher upstream.
218
+
219
+ If you use an old client that does not support modern ciphers, you can use the
220
+ ones provided by the CIS Nginx Benchmark for example:
221
+
222
+ .. code-block :: yaml
223
+
224
+ apiVersion : v1
225
+ kind : ConfigMap
226
+ data :
227
+ config.yaml : |-
228
+ apiVersion: addons.metalk8s.scality.com/v1alpha2
229
+ kind: IngressControllerConfig
230
+ spec:
231
+ config:
232
+ ssl-ciphers: "ALL:!EXP:!NULL:!ADH:!LOW:!SSLv2:!SSLv3:!MD5:!RC4"
233
+
189
234
Applying configuration
190
235
""""""""""""""""""""""
191
236
@@ -195,9 +240,10 @@ then be applied with Salt.
195
240
.. parsed-literal ::
196
241
197
242
root\@ bootstrap $ kubectl exec --kubeconfig /etc/kubernetes/admin.conf \\
198
- -n kube-system -c salt-master salt-master-bootstrap -- \\
199
- salt-run state.sls \\
200
- metalk8s.addons.nginx-ingress.deployed \\
243
+ $(kubectl --kubeconfig /etc/kubernetes/admin.conf \\
244
+ get pod -n kube-system -l app=salt-master -o name) \\
245
+ -n kube-system -c salt-master -- \\
246
+ salt-run state.sls metalk8s.addons.nginx-ingress.deployed \\
201
247
saltenv=metalk8s-|version |
202
248
203
249
0 commit comments