-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Allow kfp Client to work with service account impersonation #4661
Comments
If this is something that would be desirable, I can try to contribute it. |
Thanks @martinbomio! That sounds useful. |
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. |
This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it. |
/reopen I believe this is still an issue |
@mattnworb: You can't reopen an issue/PR unless you authored it or you are a collaborator. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What steps did you take:
Creating a
Client
from local environment when impersonating a GCP service account. Calling it with:What happened:
Following exception is thrown:
What did you expect to happen:
The client should initialize correctly when impersonating service accounts
Environment:
How did you deploy Kubeflow Pipelines (KFP)?
KFP version:
kfp-server-api==0.1.40
KFP SDK version:
kfp==0.1.40
Anything else you would like to add:
Seems like the
get_service_account_credentials
function here does not handle the case where the credentials are google.auth.impersonated_credentials.Credentials/kind bug
The text was updated successfully, but these errors were encountered: