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