Openshift TLS configuration with API Gateway Openshift TLS configuration with API Gateway kubernetes kubernetes

Openshift TLS configuration with API Gateway


With passthrough termination, encrypted traffic is sent straight tothe destination without the router providing TLS termination.Therefore no key or certificate is required.

Because your backend service is http, you should terminate SSL at edge using

termination: edge

Reference: https://docs.openshift.com/container-platform/3.9/architecture/networking/routes.html


Solved this by adding the segment:

  port:    targetPort: https  tls:    termination: passthrough

to istio ingress route configuration as the istio ingress service default configuration listens on portName: https

name: https  port: 443  protocol: TCP  targetPort: 8080