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