关于“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之前