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

Vignesh S S Sai Ramakrishna K. · Reviewed over 3 years ago

Rajesh K. · Reviewed over 3 years ago

Cássio V. · Reviewed over 3 years ago

DineshKumar V. · Reviewed over 3 years ago

Atul M. · Reviewed over 3 years ago

Satya M. · Reviewed over 3 years ago

Satisfied

Pavani B. · Reviewed over 3 years ago

Srikala P. · Reviewed over 3 years ago

Subrahmanyasaiakhil V. · Reviewed over 3 years ago

Aabhash M. · Reviewed over 3 years ago

Jainam S. · Reviewed over 3 years ago

Pustaj M. · Reviewed over 3 years ago

Tona T. · Reviewed over 3 years ago

Prabhat S. · Reviewed over 3 years ago

Christopher K. · Reviewed over 3 years ago

GABRIELE D. · Reviewed over 3 years ago

Got further - but privalidge pod created without an error.

Scott W. · Reviewed over 3 years ago

Srinivasulu T. · Reviewed over 3 years ago

This lab does not work, username 1 does not have permissions to add IAM policies to username2

Scott W. · Reviewed over 3 years ago

Thilak K. · Reviewed over 3 years ago

Suraj Y. · Reviewed over 3 years ago

Nilesh P. · Reviewed over 3 years ago

PodSecurityPolicy was deprecated in Kubernetes v1.21, and removed from Kubernetes in v1.25.

Kin L. · Reviewed over 3 years ago

Joel A. · Reviewed over 3 years ago

The test at the end of Task 2 didn't work - the Pod deployed successfully. The instructions for verifying that the Cluster has the activated policy also didn't make sense, as they don't show what the expected result is. Maybe because this functionality is deprecated? " Kubernetes has officially deprecated PodSecurityPolicy in version 1.21 and will be removed in 1.25 with no upgrade path available with this feature enabled. For additional details, please refer to https://cloud.google.com/kubernetes-engine/docs/how-to/pod-security-policies"

Eric J. · Reviewed over 3 years ago