Implementing Role-Based Access Control with Google Kubernetes Engine Reviews

Jakub K. · Reviewed over 4 years ago

Gospodin P. · Reviewed over 4 years ago

Ricardo P. · Reviewed over 4 years ago

Nilesh G. · Reviewed over 4 years ago

Christian M. · Reviewed over 4 years ago

Vasanth R. · Reviewed over 4 years ago

Aditya G. · Reviewed over 4 years ago

Bapu P. · Reviewed over 4 years ago

Bapu P. · Reviewed over 4 years ago

Phat L. · Reviewed over 4 years ago

Arjun P. · Reviewed over 4 years ago

Nazia B. · Reviewed over 4 years ago

Wilson F. · Reviewed over 4 years ago

Faced with issues during second task assessment

Artem P. · Reviewed over 4 years ago

Santiago A. · Reviewed over 4 years ago

LUCAS T. · Reviewed over 4 years ago

Jagadesh Kumar B. · Reviewed over 4 years ago

Abhijit B. · Reviewed over 4 years ago

Ashis Kumar P. · Reviewed over 4 years ago

Gokulan K. · Reviewed over 4 years ago

Dianna R. · Reviewed over 4 years ago

Trần Đ. · Reviewed over 4 years 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 over 4 years 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 over 4 years ago

Yosuke K. · Reviewed over 4 years ago