Hi all,
Trying to figure out if the Ingress Operator is able to create Routes for
Kubernetes objects when they specify a TLS section on their spec.
>From my testing Routes are automatically generated as soon as an Ingress is
>created so as long as it does not have the tls: section.
The following Ingress does work and creates 3 Routes
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: ingress-test
spec:
rules:
- host: one.apps.mycluster.com
http:
paths:
- backend:
serviceName: one-service
servicePort: 8080
- host: two.apps.mycluster.com
http:
paths:
- backend:
serviceName: two-service
servicePort: 8080
- host: three.apps.mycluster.com
http:
paths:
- backend:
serviceName: three-service
servicePort: 8080
But this one with TLS (trying to do EDGE termination) does not generate any
routes, the minute I edit the Ingress and remove a host from the TLS section,
the ingress operator creates a route for that one.
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: ingress-test
spec:
tls:
- hosts:
- one.apps.mycluster.com
secretName: secret-ingress-one
- hosts:
- two.apps.mycluster.com
secretName: secret-ingress-two
- hosts:
- three.apps.mycluster.com
secretName: secret-ingress-three
rules:
- host: one.apps.mycluster.com
http:
paths:
- backend:
serviceName: one-service
servicePort: 8080
- host: two.apps.mycluster.com
http:
paths:
- backend:
serviceName: two-service
servicePort: 8080
- host: three.apps.mycluster.com
http:
paths:
- backend:
serviceName: three-service
servicePort: 8080
Is there any specific configuration I need to make on the Ingress Operator to
have it generate routes in this case? Or is this working as expected and it
does not support it?
Thanks in advance
_______________________________________________
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
