An Introduction to Cloud Composer 3 Reviews

was kicked the first time for no reason

Jonathan L. · Reviewed أكثر من سنة ago

Gayatri W. · Reviewed أكثر من سنة ago

Sergio David Q. · Reviewed أكثر من سنة ago

SO GOD THJSI LAb BRO

Valentino Mariano S. · Reviewed أكثر من سنة ago

Wing S. · Reviewed أكثر من سنة ago

Gayatri W. · Reviewed أكثر من سنة ago

Jean T. · Reviewed أكثر من سنة ago

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

Naeim R. · Reviewed أكثر من سنة ago

Manas T. · Reviewed أكثر من سنة ago

Eslam M. · Reviewed أكثر من سنة ago

SID EL MRABET M. · Reviewed أكثر من سنة ago

Siddharth C. · Reviewed أكثر من سنة ago

Rodrigo S. · Reviewed أكثر من سنة ago

Composer Environment was never made

Abdullah S. · Reviewed أكثر من سنة ago

Zuwei H. · Reviewed أكثر من سنة ago

Praveena K. · Reviewed أكثر من سنة ago

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. · Reviewed أكثر من سنة ago

Juan Sebastian Mateo R. · Reviewed أكثر من سنة ago

Dhagudu C. · Reviewed أكثر من سنة ago

Gustavo E. · Reviewed أكثر من سنة ago

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. · Reviewed أكثر من سنة ago

Ziya E. · Reviewed أكثر من سنة ago

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

Shobhit S. · Reviewed أكثر من سنة ago

Jorge S. · Reviewed أكثر من سنة ago

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. · Reviewed أكثر من سنة ago