Implementing Role-Based Access Control with Google Kubernetes Engine Reviews

Sreekanth K. · Reviewed almost 4 years ago

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. · Reviewed almost 4 years ago

Vladyslav P. · Reviewed almost 4 years ago

David T. · Reviewed almost 4 years ago

Juliet O. · Reviewed almost 4 years ago

Nicolas M. · Reviewed almost 4 years ago

Jithin C. · Reviewed almost 4 years ago

Dmytro D. · Reviewed almost 4 years ago

Fernando C. · Reviewed almost 4 years ago

Moussa A. · Reviewed almost 4 years ago

Sergey M. · Reviewed almost 4 years ago

LOIC E. · Reviewed almost 4 years ago

Rastislav L. · Reviewed almost 4 years ago

Jerik G. · Reviewed almost 4 years ago

Thiago P. · Reviewed almost 4 years ago

Karthik B. · Reviewed almost 4 years ago

JUNG EUN S. · Reviewed almost 4 years ago

Wali H. · Reviewed almost 4 years ago

Gaspare V. · Reviewed almost 4 years ago

현지 강. · Reviewed almost 4 years ago

Sicong H. · Reviewed almost 4 years ago

하명 정. · Reviewed almost 4 years ago

jaewoo c. · Reviewed almost 4 years ago

Yang J. · Reviewed almost 4 years ago

Ihar V. · Reviewed almost 4 years ago