关于“Securing Google Kubernetes Engine with Cloud IAM and Pod Security Policies”的评价

Dhwanil T. · 已于 over 3 years前审核

GKE Y. · 已于 over 3 years前审核

Mukesh S. · 已于 over 3 years前审核

Kunal I. · 已于 over 3 years前审核

Alberto B. · 已于 over 3 years前审核

Joshua N. · 已于 over 3 years前审核

Got a 400 returned at the final step

Jonathan M. · 已于 over 3 years前审核

Georgina H. · 已于 over 3 years前审核

It took too long to create a new cluster.

Francois N. · 已于 over 3 years前审核

Ian W. · 已于 over 3 years前审核

Christopher S. · 已于 over 3 years前审核

Ryan B. · 已于 over 3 years前审核

Nathan R. · 已于 over 3 years前审核

Rosie H. · 已于 over 3 years前审核

Dusan N. · 已于 over 3 years前审核

Qianyu Z. · 已于 over 3 years前审核

samir g. · 已于 over 3 years前审核

Jorge R. · 已于 over 3 years前审核

Kevin F. · 已于 over 3 years前审核

Shyam S. · 已于 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. · 已于 over 3 years前审核

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

Athanasios P. · 已于 over 3 years前审核

Archit S. · 已于 over 3 years前审核

siva s. · 已于 over 3 years前审核

Naresh M. · 已于 over 3 years前审核