Implementing Role-Based Access Control with Google Kubernetes Engine Reviews

Oleh C. · Reviewed כמעט 3 שנים ago

Giosuè R. · Reviewed כמעט 3 שנים ago

Rajashekar M. · Reviewed כמעט 3 שנים ago

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