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