Closed neuromage closed 4 months ago
/cc @Bobgy
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.
Closing this issue. No activity for more than a year.
/close
@rimolive: Closing this issue.
Environment
How did you deploy Kubeflow Pipelines (KFP)? I used option 2 in standalone deployment
KFP version: Deployed from master branch
KFP SDK version: 1.6.4
Steps to reproduce
Security
options, enableWorkload Identity
b. Ensure you have a service account for using workload identity (e.g.workload-identity@<PROJECT-ID>.iam.gserviceaccount.com
) c. Ensure this account is bound to KSA[kubeflow/pipeline-runner]
. Example:pipeline_root
set to a GCS directory in which the workload identity service account above has write permissions.Expected result
Pipeline completes successfully.
What happened instead
Pipeline failed, with launcher complaining about lacking permissions.
Fix
Enable GKE metadata server on the default node-pool using these instructions, e.g.
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.