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

Vasanth R. · 已于 over 4 years前审核

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

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

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

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

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

Nazia B. · 已于 over 4 years前审核

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

Faced with issues during second task assessment

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

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

LUCAS T. · 已于 over 4 years前审核

Jagadesh Kumar B. · 已于 over 4 years前审核

Abhijit B. · 已于 over 4 years前审核

Ashis Kumar P. · 已于 over 4 years前审核

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

Dianna R. · 已于 over 4 years前审核

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前审核