Implementing Role-Based Access Control with Google Kubernetes Engine Reviews

Shivam S. · Reviewed 3 yıldan fazla ago

Oleh C. · Reviewed 3 yıldan fazla ago

Giosuè R. · Reviewed 3 yıldan fazla ago

Rajashekar M. · Reviewed 3 yıldan fazla ago

It's fine

Ryan C. · Reviewed 3 yıldan fazla ago

Adam N. · Reviewed 3 yıldan fazla ago

Oren L. · Reviewed 3 yıldan fazla ago

Alex D. · Reviewed 3 yıldan fazla ago

Lotem D. · Reviewed 3 yıldan fazla ago

Itay I. · Reviewed 3 yıldan fazla ago

Eyal G. · Reviewed 3 yıldan fazla ago

Liron H. · Reviewed 3 yıldan fazla ago

Bar V. · Reviewed 3 yıldan fazla ago

Prasanna A. · Reviewed 3 yıldan fazla ago

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

Vladyslav P. · Reviewed 3 yıldan fazla ago

David T. · Reviewed 3 yıldan fazla ago

Juliet O. · Reviewed 3 yıldan fazla ago

Nicolas M. · Reviewed 3 yıldan fazla ago

Jithin C. · Reviewed 3 yıldan fazla ago

Dmytro D. · Reviewed 3 yıldan fazla ago

Fernando C. · Reviewed 3 yıldan fazla ago

Moussa A. · Reviewed 3 yıldan fazla ago

Sergey M. · Reviewed 3 yıldan fazla ago