Secure ingress gateway using custom ingress gateway

#1

The link in the Istio tasks for “Secure Ingress with HTTPS” has reference to certain conventions assuming one is using the istio-ingressgateway as the service to get traffic into the mesh. But if I was using another service as the loadbalancer, what are the naming conventions to be followed for the secret and certificate paths to be correctly configured.

For example, if my new service was named “myown-ilbgateway”, how does that affect the path for the cert directories and the name for the Secret?

0 Likes

#2

Its all in the helm charts and the way you mount the secrets… There is nothing in code that mandates a particular path. https://github.com/istio/istio/blob/f62d1b4423d1c3e4a8e8118d718f50b7cd383dbe/install/kubernetes/helm/istio/charts/gateways/values.yaml#L100

0 Likes