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

Vignesh S S Sai Ramakrishna K. · Reviewed больше 3 лет ago

Rajesh K. · Reviewed больше 3 лет ago

Cássio V. · Reviewed больше 3 лет ago

DineshKumar V. · Reviewed больше 3 лет ago

Atul M. · Reviewed больше 3 лет ago

Satya M. · Reviewed больше 3 лет ago

Satisfied

Pavani B. · Reviewed больше 3 лет ago

Srikala P. · Reviewed больше 3 лет ago

Subrahmanyasaiakhil V. · Reviewed больше 3 лет ago

Aabhash M. · Reviewed больше 3 лет ago

Jainam S. · Reviewed больше 3 лет ago

Pustaj M. · Reviewed больше 3 лет ago

Tona T. · Reviewed больше 3 лет ago

Prabhat S. · Reviewed больше 3 лет ago

Christopher K. · Reviewed больше 3 лет ago

GABRIELE D. · Reviewed больше 3 лет ago

Got further - but privalidge pod created without an error.

Scott W. · Reviewed больше 3 лет ago

Srinivasulu T. · Reviewed больше 3 лет ago

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

Scott W. · Reviewed больше 3 лет ago

Thilak K. · Reviewed больше 3 лет ago

Suraj Y. · Reviewed больше 3 лет ago

Nilesh P. · Reviewed больше 3 лет ago

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

Kin L. · Reviewed больше 3 лет ago

Joel A. · Reviewed больше 3 лет 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 больше 3 лет ago