Securing Google Kubernetes Engine with Cloud IAM and Pod Security Policies Reviews

Dhwanil T. · Reviewed over 3 years ago

GKE Y. · Reviewed over 3 years ago

Mukesh S. · Reviewed over 3 years ago

Kunal I. · Reviewed over 3 years ago

Alberto B. · Reviewed over 3 years ago

Joshua N. · Reviewed over 3 years ago

Got a 400 returned at the final step

Jonathan M. · Reviewed over 3 years ago

Georgina H. · Reviewed over 3 years ago

It took too long to create a new cluster.

Francois N. · Reviewed over 3 years ago

Ian W. · Reviewed over 3 years ago

Christopher S. · Reviewed over 3 years ago

Ryan B. · Reviewed over 3 years ago

Nathan R. · Reviewed over 3 years ago

Rosie H. · Reviewed over 3 years ago

Dusan N. · Reviewed over 3 years ago

Qianyu Z. · Reviewed over 3 years ago

samir g. · Reviewed over 3 years ago

Jorge R. · Reviewed over 3 years ago

Kevin F. · Reviewed over 3 years ago

Shyam S. · Reviewed over 3 years ago

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. · Reviewed over 3 years ago

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

Athanasios P. · Reviewed over 3 years ago

Archit S. · Reviewed over 3 years ago

siva s. · Reviewed over 3 years ago

Naresh M. · Reviewed over 3 years ago