-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Seldon-Core Quickstart is not working #4958
Comments
Issue-Label Bot is automatically applying the labels:
Please mark this comment with 👍 or 👎 to give our bot feedback! |
Are you using any kind of authentication service? I posted a similar issue just now for AWS. It says here for port forwarding that authentication can be an issue: |
Yes I am using Google Identity Aware proxy when interacting with the endpoint. |
I've found a solution for the problem. Something similar to the page I linked above can be done also for the Seldon Quickstart. |
/area seldon |
/cc @cliveseldon |
I can update the docs but looks like a lot of that script is generic IAP processing. I could try to generalize it and add a Seldon specific addition? |
The only thing I've changed in the script is adding |
I'm getting the same issue even with the Python script. I've created a separate service account with access to all that is related to IAP. Could you please provide more details on how did you fix that? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Issue-Label Bot is automatically applying the labels:
Please mark this comment with 👍 or 👎 to give our bot feedback! |
It's because of the wrong service account. You need to add more permissions. Try the following: IAP-secured Web App User, |
/kind bug
What steps did you take and what happened:
After Installing Kubeflow in GKE, everything works fine part from Seldon.
I am following the quickstart example in Kubeflow Docs so I am:
when I send my prediction with:
I get:
Origin authentication failed
Inspecting the Logs of istio ingress-gateway I can see that the returned error code is 401 - Unauthorized so I think the problem is at istio ingress-gateway level.
I've tried several times with different Kubeflow versions but I am still getting the same error.
Environment:
The text was updated successfully, but these errors were encountered: