-
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
Provide argument to assign GCP service account to use for DSL operator #218
Comments
@IronPan any update on this? |
@IronPan Any update on this? What impact does this have on users? |
The work for generic DSL support to assign GCP service account is completed and being used in all our samples for a while. Thanks for following up. I'll close this one. I don't think there is a plan to have a tfjob sample but that might worth a separate discussion. |
Linchin
pushed a commit
to Linchin/pipelines
that referenced
this issue
Apr 11, 2023
magdalenakuhn17
pushed a commit
to magdalenakuhn17/pipelines
that referenced
this issue
Oct 22, 2023
HumairAK
pushed a commit
to red-hat-data-services/data-science-pipelines
that referenced
this issue
Mar 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the tf-job operator and dataflow operator don't expose parameter to assign service account
tfjob
dataflow
When we integrate with kubeflow, the user should be able to mount the service account to the container. One option is for operator to provide an parameter.
The text was updated successfully, but these errors were encountered: