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