An Introduction to Cloud Composer 3 Reviews

was kicked the first time for no reason

Jonathan L. · Reviewed 1 yıldan fazla ago

Gayatri W. · Reviewed 1 yıldan fazla ago

Sergio David Q. · Reviewed 1 yıldan fazla ago

SO GOD THJSI LAb BRO

Valentino Mariano S. · Reviewed 1 yıldan fazla ago

Wing S. · Reviewed 1 yıldan fazla ago

Gayatri W. · Reviewed 1 yıldan fazla ago

Jean T. · Reviewed 1 yıldan fazla ago

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

Naeim R. · Reviewed 1 yıldan fazla ago

Manas T. · Reviewed 1 yıldan fazla ago

Eslam M. · Reviewed 1 yıldan fazla ago

SID EL MRABET M. · Reviewed 1 yıldan fazla ago

Siddharth C. · Reviewed 1 yıldan fazla ago

Rodrigo S. · Reviewed 1 yıldan fazla ago

Composer Environment was never made

Abdullah S. · Reviewed 1 yıldan fazla ago

Zuwei H. · Reviewed 1 yıldan fazla ago

Praveena K. · Reviewed 1 yıldan fazla 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 1 yıldan fazla ago

Juan Sebastian Mateo R. · Reviewed 1 yıldan fazla ago

Dhagudu C. · Reviewed 1 yıldan fazla ago

Gustavo E. · Reviewed 1 yıldan fazla 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 1 yıldan fazla ago

Ziya E. · Reviewed 1 yıldan fazla ago

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

Shobhit S. · Reviewed 1 yıldan fazla ago

Jorge S. · Reviewed 1 yıldan fazla 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 1 yıldan fazla ago