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
Allow multiple ingress hosts to be defined when using ingress (ansible#1377)
* Replace api version for deployment kind to apps/v1
* Add new multiple ingress spec and deprecate hostname and ingress_tls_secret
* Manage new ingress_hosts.tls_secret backup separately
* Fix ci molecule lint warnings and error
* Fix documentation
* Fix ingress_hosts tls_secret key being optional
* Remove fieldDependency:ingress_type:Ingress for Ingress Hosts
* Fix scenario when neither hostname or ingress_hosts is defined
---------
Co-authored-by: Guillaume Lefevre <[email protected]>
Co-authored-by: Seth Foster <[email protected]>
Co-authored-by: Christian Adams <[email protected]>
| loadbalancer_protocol | Protocol to use for Loadbalancer ingress | http |
34
34
| loadbalancer_port | Port used for Loadbalancer ingress | 80 |
35
-
| loadbalancer_ip | Assign Loadbalancer IP | '' |
35
+
| loadbalancer_ip | Assign Loadbalancer IP | '' |
36
36
37
37
```yaml
38
38
---
@@ -86,22 +86,26 @@ spec:
86
86
87
87
The following variables are customizable when `ingress_type=ingress`. The `ingress` type creates an Ingress resource as [documented](https://kubernetes.io/docs/concepts/services-networking/ingress/) which can be shared with many other Ingress Controllers as [listed](https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/).
0 commit comments