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