-
Notifications
You must be signed in to change notification settings - Fork 825
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OIDC EnvoyFilter not working with Istio 1.3.1 #1115
Comments
Issue-Label Bot is automatically applying the labels:
Please mark this comment with 👍 or 👎 to give our bot feedback! |
/kind bug |
/area istio |
Hi @adriangonz! |
I think you are on the money @yanniszark. I was tinkering with the Closing this issue now as there doesn't seem to be a problem. |
Describe the bug:
I'm currently trying to set up a cluster with Istio and Dex using Istio 1.3.1 instead of Istio 1.1.6 (using the manifests under
istio-1-3-1
). However, I can't get the login flow to work. In particular what I see is that the/login/oidc
URL just returns a404
error. On a regular cluster (i.e. using Istio 1.1.6)/login/oidc
would just get routed to theauthservice
pod.Potential cause:
The routing of
/login/oidc
requests to theauthservice
seems to happen through anEnvoyFilter
created inistio/oidc-authservice
. However, Istio 1.3 released some changes affecting theEnvoyFilter
CRD. This means that the manifests for Istio 1.3.1 (underistio-1-3-1
) are currently incompatible with the ones underistio/oidc-authservice
.The text was updated successfully, but these errors were encountered: