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
@@ -786,14 +786,12 @@ For example, below is the config with using external TLS Secret for the Ingress
786
786
787
787
```yaml
788
788
ingress:
789
+
enableWithController: true
789
790
hostname: selenium-grid.prod.domain.com
790
791
tls:
791
792
- secretName: my-external-tls-secret
792
793
hosts:
793
794
- selenium-grid.prod.domain.com
794
-
795
-
ingress-ngnix:
796
-
enabled: true
797
795
```
798
796
799
797
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`.
@@ -802,7 +800,7 @@ For example (replace `$RELEASENAME` and `$NAMESPACE` with your values):
# Enable ingress without automatically installing Ingress NGINX Controller
132
-
enableWithExistingController: true
129
+
# Enable to create ingress resource
130
+
enabled: true
131
+
# Enable ingress resource with automatically installing Ingress NGINX Controller
132
+
enableWithController: false
133
133
# Name of ingress class to select which controller will implement ingress resource
134
134
className: ""
135
135
# Refer to list nginx annotations: https://github.com/kubernetes/ingress-nginx/blob/main/docs/user-guide/nginx-configuration/annotations.md#annotations
0 commit comments