Implementing Role-Based Access Control with Google Kubernetes Engine Reviews

Abhijit B. · Reviewed почти 5 лет ago

Ashis Kumar P. · Reviewed почти 5 лет ago

Gokulan K. · Reviewed почти 5 лет ago

Dianna R. · Reviewed почти 5 лет ago

Trần Đ. · Reviewed почти 5 лет 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 почти 5 лет 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 почти 5 лет ago

Yosuke K. · Reviewed почти 5 лет ago

Srikanth V. · Reviewed почти 5 лет ago

Romualdo L. · Reviewed почти 5 лет ago

Eric F. · Reviewed почти 5 лет ago

great

Reinaldo F. · Reviewed почти 5 лет ago

done

Shailesh S. · Reviewed почти 5 лет ago

Oleksandr M. · Reviewed почти 5 лет ago

Evan L. · Reviewed почти 5 лет ago

Richard Y. · Reviewed почти 5 лет ago

Radhakrishnan S. · Reviewed почти 5 лет ago

Ahmed G. · Reviewed почти 5 лет ago

VIALLE E. · Reviewed почти 5 лет ago

Krishna K. · Reviewed почти 5 лет ago

Good lab, less confusing then the previous one!

Pawel P. · Reviewed почти 5 лет ago

Ricardo P. · Reviewed почти 5 лет ago

Javier A. · Reviewed почти 5 лет ago

Daniel Alejandro P. · Reviewed почти 5 лет ago

CHIOVINI F. · Reviewed почти 5 лет ago