Add support for impersonation in GKEStartPodOperator, DataflowCreateJavaJobOperator and DataflowCreatePythonJobOperator
See original GitHub issueDescription
GKEStartPodOperator
, DataflowCreateJavaJobOperator
and DataflowCreatePythonJobOperator
do not support direct impersonation of a service account in Google services.
Use case / motivation
GKEStartPodOperator
, DataflowCreateJavaJobOperator
and DataflowCreatePythonJobOperator
, in contrary to other Google operators, do not use Credentials
class for authentication, so they require individual approach to support direct impersonation in them.
In case of GKEStartPodOperator
it seems it should suffice to add --impersonate-service-account
to the gcloud container clusters get-credentials
command. However, this way we will not be able to use chain of service accounts, like in the rest of Google operators.
In case of DataflowCreateJavaJobOperator
and DataflowCreatePythonJobOperator
, some changes in provide_gcp_credential_file_as_context
will probably be needed.
Related Issues
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (7 by maintainers)
@rajatsri28 Awesome! I assigned you to this ticket. 🐈
Hi @olchas , Can I pick this up?