Implementing Role-Based Access Control with Google Kubernetes Engine Reviews

Trần Đ. · Reviewed over 4 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 over 4 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 over 4 years ago

Yosuke K. · Reviewed over 4 years ago

Srikanth V. · Reviewed over 4 years ago

Romualdo L. · Reviewed over 4 years ago

Eric F. · Reviewed over 4 years ago

great

Reinaldo F. · Reviewed over 4 years ago

done

Shailesh S. · Reviewed over 4 years ago

Oleksandr M. · Reviewed over 4 years ago

Evan L. · Reviewed over 4 years ago

Richard Y. · Reviewed over 4 years ago

Radhakrishnan S. · Reviewed over 4 years ago

Ahmed G. · Reviewed over 4 years ago

VIALLE E. · Reviewed over 4 years ago

Krishna K. · Reviewed over 4 years ago

Good lab, less confusing then the previous one!

Pawel P. · Reviewed over 4 years ago

Ricardo P. · Reviewed over 4 years ago

Javier A. · Reviewed over 4 years ago

Daniel Alejandro P. · Reviewed over 4 years ago

CHIOVINI F. · Reviewed over 4 years ago

Eduardo K. · Reviewed over 4 years ago

CHIOVINI F. · Reviewed over 4 years ago

Frank F. · Reviewed over 4 years ago

Jocki H. · Reviewed over 4 years ago