Uma introdução ao Cloud Composer 3 avaliações

Kevin Mateo C. · Revisado há over 1 year

Omkar K. · Revisado há over 1 year

Sameer S. · Revisado há over 1 year

Christoph K. · Revisado há over 1 year

GIRISH KUMAR S. · Revisado há over 1 year

Kishore P. · Revisado há over 1 year

Aswathi M. · Revisado há over 1 year

Sri Lakshmi G. · Revisado há over 1 year

Anton S. · Revisado há over 1 year

Camille P. · Revisado há over 1 year

Jan Daniel G. · Revisado há over 1 year

Kuo-Shiang H. · Revisado há over 1 year

Kuo-Shiang H. · Revisado há over 1 year

Ali M. · Revisado há over 1 year

Higor C. · Revisado há over 1 year

Farouk I. · Revisado há over 1 year

Edelmiro F. · Revisado há over 1 year

Fernanda Denisse T. · Revisado há over 1 year

Kendall R. · Revisado há over 1 year

Krzysztof P. · Revisado há over 1 year

Andrew P. · Revisado há over 1 year

Challa J. · Revisado há over 1 year

Jung M. · Revisado há over 1 year

The following Error Occured: Some of the GKE pods failed to become healthy. Please check the GKE logs for details, and retry the operation. The issue may be caused by missing IAM roles in the following Service Accounts: - service-530416650466@cloudcomposer-accounts.iam.gserviceaccount.com in project 530416650466 is missing role roles/composer.ServiceAgentV2Ext The list of missing roles is generated without checking individual permissions in IAM custom roles. If any of the Service Accounts above uses custom IAM roles, its permissions may be sufficient and a corresponding warning may be ignored. I ensured I followed all steps correctly. On top of this it took 45 mins to spin the cluster up and return this error so was a bit frustrating

Bruno C. · Revisado há over 1 year

Mousumi M. · Revisado há over 1 year