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

Vignesh S S Sai Ramakrishna K. · Reviewed 3 yıldan fazla ago

Rajesh K. · Reviewed 3 yıldan fazla ago

Cássio V. · Reviewed 3 yıldan fazla ago

DineshKumar V. · Reviewed 3 yıldan fazla ago

Atul M. · Reviewed 3 yıldan fazla ago

Satya M. · Reviewed 3 yıldan fazla ago

Satisfied

Pavani B. · Reviewed 3 yıldan fazla ago

Srikala P. · Reviewed 3 yıldan fazla ago

Subrahmanyasaiakhil V. · Reviewed 3 yıldan fazla ago

Aabhash M. · Reviewed 3 yıldan fazla ago

Jainam S. · Reviewed 3 yıldan fazla ago

Pustaj M. · Reviewed 3 yıldan fazla ago

Tona T. · Reviewed 3 yıldan fazla ago

Prabhat S. · Reviewed 3 yıldan fazla ago

Christopher K. · Reviewed 3 yıldan fazla ago

GABRIELE D. · Reviewed 3 yıldan fazla ago

Got further - but privalidge pod created without an error.

Scott W. · Reviewed 3 yıldan fazla ago

Srinivasulu T. · Reviewed 3 yıldan fazla ago

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

Scott W. · Reviewed 3 yıldan fazla ago

Thilak K. · Reviewed 3 yıldan fazla ago

Suraj Y. · Reviewed 3 yıldan fazla ago

Nilesh P. · Reviewed 3 yıldan fazla ago

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

Kin L. · Reviewed 3 yıldan fazla ago

Joel A. · Reviewed 3 yıldan fazla 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 yıldan fazla ago