Implementing Role-Based Access Control with Google Kubernetes Engine Reviews

It's fine

Ryan C. · Reviewed около 3 лет ago

Adam N. · Reviewed около 3 лет ago

Oren L. · Reviewed около 3 лет ago

Alex D. · Reviewed около 3 лет ago

Lotem D. · Reviewed около 3 лет ago

Itay I. · Reviewed около 3 лет ago

Eyal G. · Reviewed около 3 лет ago

Liron H. · Reviewed около 3 лет ago

Bar V. · Reviewed около 3 лет ago

Prasanna A. · Reviewed около 3 лет ago

Sreekanth K. · Reviewed около 3 лет 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 около 3 лет ago

Vladyslav P. · Reviewed около 3 лет ago

David T. · Reviewed около 3 лет ago

Juliet O. · Reviewed около 3 лет ago

Nicolas M. · Reviewed около 3 лет ago

Jithin C. · Reviewed около 3 лет ago

Dmytro D. · Reviewed около 3 лет ago

Fernando C. · Reviewed около 3 лет ago

Moussa A. · Reviewed около 3 лет ago

Sergey M. · Reviewed около 3 лет ago

LOIC E. · Reviewed около 3 лет ago

Rastislav L. · Reviewed около 3 лет ago

Jerik G. · Reviewed около 3 лет ago

Thiago P. · Reviewed около 3 лет ago