faint-lion-81580
04/25/2023, 12:26 AM@kubernetes
step failed to start with a 403 (GCS object forbidden). I ran the flow as a user that has permissions to assume the service account identity (and also tried the other method of using the key in metaflow_gsa_key_default.json
). The permissions on the service account look correct. When I describe the pod, the service account listed is default
. The gsa-metaflow-default
service account shows up as default in cloud console. Any ideas on what else to try?