Implementing Role-Based Access Control with Google Kubernetes Engine Reviews

It's fine

Ryan C. · Reviewed about 3 years ago

Adam N. · Reviewed about 3 years ago

Oren L. · Reviewed about 3 years ago

Alex D. · Reviewed about 3 years ago

Lotem D. · Reviewed about 3 years ago

Itay I. · Reviewed about 3 years ago

Eyal G. · Reviewed about 3 years ago

Liron H. · Reviewed about 3 years ago

Bar V. · Reviewed about 3 years ago

Prasanna A. · Reviewed about 3 years ago

Sreekanth K. · Reviewed about 3 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 about 3 years ago

Vladyslav P. · Reviewed about 3 years ago

David T. · Reviewed about 3 years ago

Juliet O. · Reviewed about 3 years ago

Nicolas M. · Reviewed about 3 years ago

Jithin C. · Reviewed about 3 years ago

Dmytro D. · Reviewed about 3 years ago

Fernando C. · Reviewed about 3 years ago

Moussa A. · Reviewed about 3 years ago

Sergey M. · Reviewed about 3 years ago

LOIC E. · Reviewed about 3 years ago

Rastislav L. · Reviewed about 3 years ago

Jerik G. · Reviewed about 3 years ago

Thiago P. · Reviewed about 3 years ago