Implementing Role-Based Access Control with Google Kubernetes Engine Reviews

Oleh C. · Reviewed neredeyse 3 yıl ago

Giosuè R. · Reviewed neredeyse 3 yıl ago

Rajashekar M. · Reviewed neredeyse 3 yıl ago

It's fine

Ryan C. · Reviewed neredeyse 3 yıl ago

Adam N. · Reviewed neredeyse 3 yıl ago

Oren L. · Reviewed neredeyse 3 yıl ago

Alex D. · Reviewed neredeyse 3 yıl ago

Lotem D. · Reviewed neredeyse 3 yıl ago

Itay I. · Reviewed neredeyse 3 yıl ago

Eyal G. · Reviewed neredeyse 3 yıl ago

Liron H. · Reviewed neredeyse 3 yıl ago

Bar V. · Reviewed neredeyse 3 yıl ago

Prasanna A. · Reviewed neredeyse 3 yıl ago

Sreekanth K. · Reviewed neredeyse 3 yıl 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 neredeyse 3 yıl ago

Vladyslav P. · Reviewed neredeyse 3 yıl ago

David T. · Reviewed neredeyse 3 yıl ago

Juliet O. · Reviewed neredeyse 3 yıl ago

Nicolas M. · Reviewed neredeyse 3 yıl ago

Jithin C. · Reviewed neredeyse 3 yıl ago

Dmytro D. · Reviewed neredeyse 3 yıl ago

Fernando C. · Reviewed neredeyse 3 yıl ago

Moussa A. · Reviewed neredeyse 3 yıl ago

Sergey M. · Reviewed neredeyse 3 yıl ago

LOIC E. · Reviewed neredeyse 3 yıl ago