Implementing Role-Based Access Control with Google Kubernetes Engine Reviews

Aishwary D. · Reviewed больше 3 лет ago

nice lab

wahyu t. · Reviewed больше 3 лет ago

11/11/2022- first attempt role based access control is not working, followed all the instruction.

Srinivasan V. · Reviewed больше 3 лет ago

岡村 恵. · Reviewed больше 3 лет ago

Shivam S. · Reviewed больше 3 лет ago

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