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
# `ingress.nginx.proxyBuffer.number` pass value to annotation(s)
283
283
nginx.ingress.kubernetes.io/proxy-buffers-number
284
-
```
285
-
286
-
You can generate a test double self-signed certificate specify for your `hostname`, assign it to spec `ingress.tls` and NGINX ingress controller default certificate (if it is enabled inline). For example:
287
284
288
-
```yaml
289
-
tls:
290
-
ingress:
291
-
generateTLS: true
285
+
# `ingress.nginx.websocket` pass boolean value to add backend service has WebSocket request (Hub/Router - noVNC, CDP, etc.)
Refer to [NGINX Ingress Controller Annotations](https://github.com/kubernetes/ingress-nginx/blob/main/docs/user-guide/nginx-configuration/annotations.md) for more details.
298
+
299
+
Refer to below section [Configuration of Secure Communication] for more details on how to configure secure communication to Ingress proxy.
300
+
303
301
## Configuration
304
302
305
303
### Configuration global
@@ -656,7 +654,7 @@ There are multiple ways to insert your certificate, private key, truststore to t
656
654
```bash
657
655
# Steps to prepare your self-signed certificate
658
656
./certs/cert.sh -d /path/to/your/
659
-
# Create TLS Secret with your certificate, private key, truststore
657
+
# Create TLS Secret with your certificate, private key, truststore (or a Secret type kubernetes.io/tls)
In additional, if the ingress is enabled, and approach SSL Passthrough is used to ensure the request forwards to the backend components via an encrypted connection.
691
-
With `ingress.hostname` is set, the default server TLS secret is also used for hosts TLS secretName when `ingress.tls` is empty. Once you specify `ingress.tls`, your specified secret will be used for hosts TLS secretName.
689
+
With `ingress.hostname` is set, the default server TLS secret is also used for hosts TLS secretName when `ingress.tls` is empty. Once you specify `ingress.tls`, your specified secret will be used for hosts TLS secretName. For example
Moreover, when sub-chart `ingress-nginx` is enabled (deploy Ingress NGINX Controller together), the default server TLS secret can also be assigned via `ingress-nginx.controller.extraArgs.default-ssl-certificate`.
696
-
For example (replace `$RELEASENAME` and `$NAMESPACE` with your values):
Below is an example of Grid UI accessible via NodePort with secure connection, and using external TLS Secret (replace `$RELEASENAME` and `$NAMESPACE` with your values):
In additional, a self-signed certificate and private key can be generated runtime during the chart deployment for Ingress TLS by setting these values (replace `$RELEASENAME` with your value):
728
+
In additional, a self-signed certificate and private key can be generated runtime during the chart deployment for Ingress TLS by setting these values:
You can get the `tls.crt` and `tls.key` from the Secret after the chart is deployed. For example (replace `$RELEASENAME` and `$NAMESPACE` with your values):
Grid UI can be accessed via HTTPS address `https://selenium-grid.prod.domain.com`.
775
767
768
+
Inline config TLS for the Ingress resource is also considered as enable secure connection to the Ingress proxy.
769
+
For example, below is the config with using external TLS Secret for the Ingress resource and enable sub-chart NGINX Ingress Controller:
770
+
771
+
```yaml
772
+
ingress:
773
+
hostname: selenium-grid.prod.domain.com
774
+
tls:
775
+
- secretName: my-external-tls-secret
776
+
hosts:
777
+
- selenium-grid.prod.domain.com
778
+
779
+
ingress-ngnix:
780
+
enabled: true
781
+
```
782
+
783
+
In case the Ingress resource is configured without `hostname` and `tls`, the incoming traffic access via `global.K8S_PUBLIC_IP`. When sub-chart `ingress-nginx` is enabled (deploy Ingress NGINX Controller together), the default TLS secret can also be assigned via `ingress-nginx.controller.extraArgs.default-ssl-certificate`.
784
+
For example (replace `$RELEASENAME` and `$NAMESPACE` with your values):
To enable secure in the node registration to make sure that the node is one you control and not a rouge node, you can enable and provide a registration secret string to Distributor, Router and
0 commit comments