Using Cloud SQL with Google Kubernetes Engine and Workload Identity Ulasan

Sumeet U. · Diulas 3 bulan lalu

Raj G. · Diulas 3 bulan lalu

Time too short to finish and understand the lab

Junru W. · Diulas 3 bulan lalu

Alex P. · Diulas 3 bulan lalu

Ramya C. · Diulas 3 bulan lalu

Allen B. · Diulas 3 bulan lalu

Tamas N. · Diulas 3 bulan lalu

Çetin Ç. · Diulas 3 bulan lalu

William Y. · Diulas 3 bulan lalu

Viviane G. · Diulas 3 bulan lalu

RYAN C. · Diulas 3 bulan lalu

CALEB H. · Diulas 3 bulan lalu

Yacine B. · Diulas 3 bulan lalu

David G. · Diulas 3 bulan lalu

done

Amol Z. · Diulas 3 bulan lalu

Debi M. · Diulas 3 bulan lalu

Sudhanshu M. · Diulas 3 bulan lalu

Arbaz Ahmed A. · Diulas 3 bulan lalu

Amit S. · Diulas 3 bulan lalu

Sudhir M. · Diulas 3 bulan lalu

Vineet T. · Diulas 3 bulan lalu

Balaji V. · Diulas 3 bulan lalu

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

Albert F. · Diulas 3 bulan lalu

Craig F. · Diulas 3 bulan lalu

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. · Diulas 3 bulan lalu