关于“Using Cloud SQL with Google Kubernetes Engine and Workload Identity”的评价

Sumeet U. · 已于 3 months前审核

Raj G. · 已于 3 months前审核

Time too short to finish and understand the lab

Junru W. · 已于 3 months前审核

Alex P. · 已于 3 months前审核

Ramya C. · 已于 3 months前审核

Allen B. · 已于 3 months前审核

Tamas N. · 已于 3 months前审核

Çetin Ç. · 已于 3 months前审核

William Y. · 已于 3 months前审核

Viviane G. · 已于 3 months前审核

RYAN C. · 已于 3 months前审核

CALEB H. · 已于 3 months前审核

Yacine B. · 已于 3 months前审核

David G. · 已于 3 months前审核

done

Amol Z. · 已于 3 months前审核

Debi M. · 已于 3 months前审核

Sudhanshu M. · 已于 3 months前审核

Arbaz Ahmed A. · 已于 3 months前审核

Amit S. · 已于 3 months前审核

Sudhir M. · 已于 3 months前审核

Vineet T. · 已于 3 months前审核

Balaji V. · 已于 3 months前审核

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

Albert F. · 已于 3 months前审核

Craig F. · 已于 3 months前审核

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. · 已于 3 months前审核