Implementing Role-Based Access Control with Google Kubernetes Engine Reviews

Oleh C. · Reviewed almost 3 years ago

Giosuè R. · Reviewed almost 3 years ago

Rajashekar M. · Reviewed almost 3 years ago

It's fine

Ryan C. · Reviewed almost 3 years ago

Adam N. · Reviewed almost 3 years ago

Oren L. · Reviewed almost 3 years ago

Alex D. · Reviewed almost 3 years ago

Lotem D. · Reviewed almost 3 years ago

Itay I. · Reviewed almost 3 years ago

Eyal G. · Reviewed almost 3 years ago

Liron H. · Reviewed almost 3 years ago

Bar V. · Reviewed almost 3 years ago

Prasanna A. · Reviewed almost 3 years ago

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

Vladyslav P. · Reviewed almost 3 years ago

David T. · Reviewed almost 3 years ago

Juliet O. · Reviewed almost 3 years ago

Nicolas M. · Reviewed almost 3 years ago

Jithin C. · Reviewed almost 3 years ago

Dmytro D. · Reviewed almost 3 years ago

Fernando C. · Reviewed almost 3 years ago

Moussa A. · Reviewed almost 3 years ago

Sergey M. · Reviewed almost 3 years ago

LOIC E. · Reviewed almost 3 years ago