Implementing Role-Based Access Control with Google Kubernetes Engine Reviews

Vasanth R. · Reviewed больше 4 лет ago

Aditya G. · Reviewed больше 4 лет ago

Bapu P. · Reviewed больше 4 лет ago

Bapu P. · Reviewed больше 4 лет ago

Phat L. · Reviewed больше 4 лет ago

Arjun P. · Reviewed больше 4 лет ago

Nazia B. · Reviewed больше 4 лет ago

Wilson F. · Reviewed больше 4 лет ago

Faced with issues during second task assessment

Artem P. · Reviewed больше 4 лет ago

Santiago A. · Reviewed больше 4 лет ago

LUCAS T. · Reviewed больше 4 лет ago

Jagadesh Kumar B. · Reviewed больше 4 лет ago

Abhijit B. · Reviewed больше 4 лет ago

Ashis Kumar P. · Reviewed больше 4 лет ago

Gokulan K. · Reviewed больше 4 лет ago

Dianna R. · Reviewed больше 4 лет ago

Trần Đ. · Reviewed больше 4 лет 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 лет 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 лет ago

Yosuke K. · Reviewed больше 4 лет ago

Srikanth V. · Reviewed больше 4 лет ago

Romualdo L. · Reviewed больше 4 лет ago

Eric F. · Reviewed больше 4 лет ago

great

Reinaldo F. · Reviewed больше 4 лет ago

done

Shailesh S. · Reviewed больше 4 лет ago