Implementing Role-Based Access Control with Google Kubernetes Engine Reviews

Vasanth R. · Reviewed 4 yıldan fazla ago

Aditya G. · Reviewed 4 yıldan fazla ago

Bapu P. · Reviewed 4 yıldan fazla ago

Bapu P. · Reviewed 4 yıldan fazla ago

Phat L. · Reviewed 4 yıldan fazla ago

Arjun P. · Reviewed 4 yıldan fazla ago

Nazia B. · Reviewed 4 yıldan fazla ago

Wilson F. · Reviewed 4 yıldan fazla ago

Faced with issues during second task assessment

Artem P. · Reviewed 4 yıldan fazla ago

Santiago A. · Reviewed 4 yıldan fazla ago

LUCAS T. · Reviewed 4 yıldan fazla ago

Jagadesh Kumar B. · Reviewed 4 yıldan fazla ago

Abhijit B. · Reviewed 4 yıldan fazla ago

Ashis Kumar P. · Reviewed 4 yıldan fazla ago

Gokulan K. · Reviewed 4 yıldan fazla ago

Dianna R. · Reviewed 4 yıldan fazla ago

Trần Đ. · Reviewed 4 yıldan fazla 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 4 yıldan fazla 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 4 yıldan fazla ago

Yosuke K. · Reviewed 4 yıldan fazla ago

Srikanth V. · Reviewed 4 yıldan fazla ago

Romualdo L. · Reviewed 4 yıldan fazla ago

Eric F. · Reviewed 4 yıldan fazla ago

great

Reinaldo F. · Reviewed 4 yıldan fazla ago

done

Shailesh S. · Reviewed 4 yıldan fazla ago