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