Istio (Envoy) + Cert-Manager + Let’s Encrypt for TLS guide does not work with Istio 0.8.0 any more ...
The problem is that Istio 0.8.0 no longer support combining Kubernetes Ingress specs with Istio routing rules. So we can't create an ingress for /.well-known/acme-challenge/.* path and map it in the gateway.
I've tried to create mTLS setup for cert-manager and add Gateway/VirtualService. The problem here is that cert-manager create a cm-acme-http-solver-xxx pod in the istio-system namespace, which does not have the sidecard inject label...
Is there a solution for Istio 0.8.0 + CertManager 0.3.0? Some alternative solution would be also great...
Istio (Envoy) + Cert-Manager + Let’s Encrypt for TLS guide does not work with Istio 0.8.0 any more ...
The problem is that Istio 0.8.0 no longer support combining Kubernetes Ingress specs with Istio routing rules. So we can't create an ingress for
/.well-known/acme-challenge/.*path and map it in the gateway.I've tried to create mTLS setup for cert-manager and add Gateway/VirtualService. The problem here is that cert-manager create a cm-acme-http-solver-xxx pod in the
istio-systemnamespace, which does not have the sidecard inject label...Is there a solution for Istio 0.8.0 + CertManager 0.3.0? Some alternative solution would be also great...