关于“Implementing Role-Based Access Control with Google Kubernetes Engine”的评价

Oleh C. · 评论almost 3 years之前

Giosuè R. · 评论almost 3 years之前

Rajashekar M. · 评论almost 3 years之前

It's fine

Ryan C. · 评论almost 3 years之前

Adam N. · 评论almost 3 years之前

Oren L. · 评论almost 3 years之前

Alex D. · 评论almost 3 years之前

Lotem D. · 评论almost 3 years之前

Itay I. · 评论almost 3 years之前

Eyal G. · 评论almost 3 years之前

Liron H. · 评论almost 3 years之前

Bar V. · 评论almost 3 years之前

Prasanna A. · 评论almost 3 years之前

Sreekanth K. · 评论almost 3 years之前

This will fail indicating that Username 2 does not have the correct permission to create Pods. Username 2 only has the viewer permissions it started the lab with at this point because you have not bound any other role to that account yet. Because K8S RBAC is distinct from GCP IAM, this isn't a full explanation. It would be nice to more thoroughly investigate the cluster role bindings to fully explain why USER_1 can deploy production pods but USER_2 cannot.

Justin P. · 评论almost 3 years之前

Vladyslav P. · 评论almost 3 years之前

David T. · 评论almost 3 years之前

Juliet O. · 评论almost 3 years之前

Nicolas M. · 评论almost 3 years之前

Jithin C. · 评论almost 3 years之前

Dmytro D. · 评论almost 3 years之前

Fernando C. · 评论almost 3 years之前

Moussa A. · 评论almost 3 years之前

Sergey M. · 评论almost 3 years之前

LOIC E. · 评论almost 3 years之前