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
Egress gateway Helm template contains istio.default as the secret name, should be istio.istio-egressgateway-service-account. The bug is fixed in master by #6350 on master , I would like to have it in 0.8.1.
Due to the wrong secret name, mTLS between a sidecar proxy and the egress gateway will fail.
Expected behavior
Directing egress traffic from an application pod to the egress gateway should work when Istio is deployed with mTLS.
Steps to reproduce the bug
Follow the steps in istio/istio.io#1605 for Istio with mTLS.
Version
The release 0.8.0.
Is Istio Auth enabled or not?
Yes.
Environment
Kubernetes.
The text was updated successfully, but these errors were encountered:
Describe the bug
Egress gateway Helm template contains
istio.default
as the secret name, should beistio.istio-egressgateway-service-account
. The bug is fixed in master by #6350 on master , I would like to have it in 0.8.1.Due to the wrong secret name, mTLS between a sidecar proxy and the egress gateway will fail.
Expected behavior
Directing egress traffic from an application pod to the egress gateway should work when Istio is deployed with mTLS.
Steps to reproduce the bug
Follow the steps in istio/istio.io#1605 for Istio with mTLS.
Version
The release 0.8.0.
Is Istio Auth enabled or not?
Yes.
Environment
Kubernetes.
The text was updated successfully, but these errors were encountered: