Implementing Role-Based Access Control with Google Kubernetes Engine Reviews

Abhijit B. · Reviewed almost 5 years ago

Ashis Kumar P. · Reviewed almost 5 years ago

Gokulan K. · Reviewed almost 5 years ago

Dianna R. · Reviewed almost 5 years ago

Trần Đ. · Reviewed almost 5 years ago

The role and rolebinding do not work on user 2. I'm sure to have edited the provided file with the user2 email. The attempt of pod creation has this output: <user2>@cloudshell:~/ak8s/RBAC (<project_id>)$ kubectl create -f ./production-pod.yaml Error from server (Forbidden): error when creating "./production-pod.yaml": pods is forbidden: User "<user2_email>" cannot create resource "pods" in API group "" in the namespace "production": requires one of ["container.pods.create"] permission(s).

Riccardo C. · Reviewed almost 5 years ago

Last verification step didn't work. The check functionality really needs to be improved. Here are my pods kubectl get pods --namespace production NAME READY STATUS RESTARTS AGE nginx 1/1 Running 0 10m production-pod 1/1 Running 0 80s

Tim W. · Reviewed almost 5 years ago

Yosuke K. · Reviewed almost 5 years ago

Srikanth V. · Reviewed almost 5 years ago

Romualdo L. · Reviewed almost 5 years ago

Eric F. · Reviewed almost 5 years ago

great

Reinaldo F. · Reviewed almost 5 years ago

done

Shailesh S. · Reviewed almost 5 years ago

Oleksandr M. · Reviewed almost 5 years ago

Evan L. · Reviewed almost 5 years ago

Richard Y. · Reviewed almost 5 years ago

Radhakrishnan S. · Reviewed almost 5 years ago

Ahmed G. · Reviewed almost 5 years ago

VIALLE E. · Reviewed almost 5 years ago

Krishna K. · Reviewed almost 5 years ago

Good lab, less confusing then the previous one!

Pawel P. · Reviewed almost 5 years ago

Ricardo P. · Reviewed almost 5 years ago

Javier A. · Reviewed almost 5 years ago

Daniel Alejandro P. · Reviewed almost 5 years ago

CHIOVINI F. · Reviewed almost 5 years ago