Proteger o Google Kubernetes Engine com o Cloud IAM e políticas de segurança de pods avaliações

Dhwanil T. · Revisado há over 3 years

GKE Y. · Revisado há over 3 years

Mukesh S. · Revisado há over 3 years

Kunal I. · Revisado há over 3 years

Alberto B. · Revisado há over 3 years

Joshua N. · Revisado há over 3 years

Got a 400 returned at the final step

Jonathan M. · Revisado há over 3 years

Georgina H. · Revisado há over 3 years

It took too long to create a new cluster.

Francois N. · Revisado há over 3 years

Ian W. · Revisado há over 3 years

Christopher S. · Revisado há over 3 years

Ryan B. · Revisado há over 3 years

Nathan R. · Revisado há over 3 years

Rosie H. · Revisado há over 3 years

Dusan N. · Revisado há over 3 years

Qianyu Z. · Revisado há over 3 years

samir g. · Revisado há over 3 years

Jorge R. · Revisado há over 3 years

Kevin F. · Revisado há over 3 years

Shyam S. · Revisado há over 3 years

ambiguity in last steps: "Test the Pod Security Policy" was able to deploy the privileged pod, although the pod security policy was in place and the controller as enabled as confirmed from: gcloud beta container clusters describe $my_cluster --zone=$my_zone --format json | jq '.podSecurityPolicyConfig' "Rotate IP Address and Credentials" After running the "start-credential-rotation" command successfully, GKE serves the cluster only to new IP and attempting to run the "complete-credential-rotation" command user is getting an error mentioning the default-pool needs to be recreated

Athanasios P. · Revisado há over 3 years

ambiguity in last steps. I have the impression that GKE doesn't need anymore the complete-rotation step

Athanasios P. · Revisado há over 3 years

Archit S. · Revisado há over 3 years

siva s. · Revisado há over 3 years

Naresh M. · Revisado há over 3 years