关于“Using Cloud SQL with Google Kubernetes Engine and Workload Identity”的评价
正在加载…
未找到任何结果。

    关于“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之前

    我们无法确保发布的评价来自已购买或已使用产品的消费者。评价未经 Google 核实。