Skip to content

Conversation

@ddl-ebrown
Copy link
Contributor

  • DOM-54018 Allow GCP access to flyte-dataplane IAM
  • DOM-54018 not sure how this will work

 - Allow GCP tokens with a custom audience matching the string
   {deploy_id}-flyte-gcp-{random_id} to access Flyte blobs

   Inspired by policy definition at
   https://jason-umiker.medium.com/cross-cloud-identities-between-gcp-and-aws-from-gke-and-or-eks-182652bddadb

   NOTE: jwt validation usually takes into account several factors

   - issuer
   - audience
   - signature
   - subject
   - scope
   - custom claims

   This policy verifies only the "aud" claim in the token, which in
   theory is spoofable by anyone using GCP to produce tokens. Therefore,
   include a random piece of data in the "aud" value that only the
   control plane will know. When generating executions on remote data
   planes (by dispatcher / workload operator), this value will be passed
   so that tokens produced from GCP will have this shared value.

   To do so requires exporting the value from the terraform code into
   the catalog and through to Nucleus
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants