Using Cloud SQL with Google Kubernetes Engine and Workload Identity Reviews

Sumeet U. · Reviewed about 1 month ago

Raj G. · Reviewed about 1 month ago

Time too short to finish and understand the lab

Junru W. · Reviewed about 1 month ago

Alex P. · Reviewed about 1 month ago

Ramya C. · Reviewed about 1 month ago

Allen B. · Reviewed about 1 month ago

Tamas N. · Reviewed about 1 month ago

Çetin Ç. · Reviewed about 1 month ago

William Y. · Reviewed about 1 month ago

Viviane G. · Reviewed about 1 month ago

RYAN C. · Reviewed about 1 month ago

CALEB H. · Reviewed about 1 month ago

Yacine B. · Reviewed about 1 month ago

David G. · Reviewed about 1 month ago

done

Amol Z. · Reviewed about 1 month ago

Debi M. · Reviewed about 1 month ago

Sudhanshu M. · Reviewed about 1 month ago

Arbaz Ahmed A. · Reviewed about 1 month ago

Amit S. · Reviewed about 1 month ago

Sudhir M. · Reviewed about 1 month ago

Vineet T. · Reviewed about 1 month ago

Balaji V. · Reviewed about 1 month ago

VEry usefule to understand the connection stalbishment between GKE workloads and Cloud SQL, and also to understand Workload Identity set up.

Albert F. · Reviewed about 1 month ago

Craig F. · Reviewed about 1 month ago

If the connection to the mysql is authenticated by using a workload identity/service account, why do I still have to proivde WORDPRESS_DB_USER and WORDPRESS_DB_PASSWORD and WORDPRESS_DB_USER and WORDPRESS_DB_USER in the deployment? Isn't the whole idea of workload identities to get rid of the passwords?

Jerome W. · Reviewed about 1 month ago