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

was kicked the first time for no reason

Jonathan L. · Revisado há over 1 year

Gayatri W. · Revisado há over 1 year

Sergio David Q. · Revisado há over 1 year

SO GOD THJSI LAb BRO

Valentino Mariano S. · Revisado há over 1 year

Wing S. · Revisado há over 1 year

Gayatri W. · Revisado há over 1 year

Jean T. · Revisado há over 1 year

There is a problem with lack of IAM in this Lab. I could not create a Composer.

Naeim R. · Revisado há over 1 year

Manas T. · Revisado há over 1 year

Eslam M. · Revisado há over 1 year

SID EL MRABET M. · Revisado há over 1 year

Siddharth C. · Revisado há over 1 year

Rodrigo S. · Revisado há over 1 year

Composer Environment was never made

Abdullah S. · Revisado há over 1 year

Zuwei H. · Revisado há over 1 year

Praveena K. · Revisado há over 1 year

Composer API Service Agent service account (service-769851901475@cloudcomposer-accounts.iam.gserviceaccount.com) does not have required permissions set. Cloud Composer API Service Agent role is missing. Please bind roles/composer.serviceAgent back on service-769851901475@cloudcomposer-accounts.iam.gserviceaccount.com.

Jer Wei Y. · Revisado há over 1 year

Juan Sebastian Mateo R. · Revisado há over 1 year

Dhagudu C. · Revisado há over 1 year

Gustavo E. · Revisado há over 1 year

This lab stack in creating of the composer and end the lab automatically falsly accusin me that that I am not following instructions. If you are interested I can show a recording. I have recorded it in case you ask, because the lab failed couple of times already.

Erdal M. · Revisado há over 1 year

Ziya E. · Revisado há over 1 year

After given all composer IAM roles then the composer environment get created successfully.

Shobhit S. · Revisado há over 1 year

Jorge S. · Revisado há over 1 year

CREATE operation on this environment failed 1 minute ago with the following error message: 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-590735423637@cloudcomposer-accounts.iam.gserviceaccount.com in project 590735423637 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.

Shobhit S. · Revisado há over 1 year