关于“Implementing Role-Based Access Control with Google Kubernetes Engine”的评价

Trần Đ. · 已于 over 4 years前审核

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. · 已于 over 4 years前审核

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. · 已于 over 4 years前审核

Yosuke K. · 已于 over 4 years前审核

Srikanth V. · 已于 over 4 years前审核

Romualdo L. · 已于 over 4 years前审核

Eric F. · 已于 over 4 years前审核

great

Reinaldo F. · 已于 over 4 years前审核

done

Shailesh S. · 已于 over 4 years前审核

Oleksandr M. · 已于 over 4 years前审核

Evan L. · 已于 over 4 years前审核

Richard Y. · 已于 over 4 years前审核

Radhakrishnan S. · 已于 over 4 years前审核

Ahmed G. · 已于 over 4 years前审核

VIALLE E. · 已于 over 4 years前审核

Krishna K. · 已于 over 4 years前审核

Good lab, less confusing then the previous one!

Pawel P. · 已于 over 4 years前审核

Ricardo P. · 已于 over 4 years前审核

Javier A. · 已于 over 4 years前审核

Daniel Alejandro P. · 已于 over 4 years前审核

CHIOVINI F. · 已于 over 4 years前审核

Eduardo K. · 已于 over 4 years前审核

CHIOVINI F. · 已于 over 4 years前审核

Frank F. · 已于 over 4 years前审核

Jocki H. · 已于 over 4 years前审核