Como implementar o controle de acesso baseado em papéis com o Google Kubernetes Engine avaliações

Vasanth R. · Revisado há over 4 years

Aditya G. · Revisado há over 4 years

Bapu P. · Revisado há over 4 years

Bapu P. · Revisado há over 4 years

Phat L. · Revisado há over 4 years

Arjun P. · Revisado há over 4 years

Nazia B. · Revisado há over 4 years

Wilson F. · Revisado há over 4 years

Faced with issues during second task assessment

Artem P. · Revisado há over 4 years

Santiago A. · Revisado há over 4 years

LUCAS T. · Revisado há over 4 years

Jagadesh Kumar B. · Revisado há over 4 years

Abhijit B. · Revisado há over 4 years

Ashis Kumar P. · Revisado há over 4 years

Gokulan K. · Revisado há over 4 years

Dianna R. · Revisado há over 4 years

Trần Đ. · Revisado há over 4 years

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. · Revisado há over 4 years

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. · Revisado há over 4 years

Yosuke K. · Revisado há over 4 years

Srikanth V. · Revisado há over 4 years

Romualdo L. · Revisado há over 4 years

Eric F. · Revisado há over 4 years

great

Reinaldo F. · Revisado há over 4 years

done

Shailesh S. · Revisado há over 4 years