Proteger o Google Kubernetes Engine com o Cloud IAM e políticas de segurança de pods avaliações

Vignesh S S Sai Ramakrishna K. · Revisado há over 3 years

Rajesh K. · Revisado há over 3 years

Cássio V. · Revisado há over 3 years

DineshKumar V. · Revisado há over 3 years

Atul M. · Revisado há over 3 years

Satya M. · Revisado há over 3 years

Satisfied

Pavani B. · Revisado há over 3 years

Srikala P. · Revisado há over 3 years

Subrahmanyasaiakhil V. · Revisado há over 3 years

Aabhash M. · Revisado há over 3 years

Jainam S. · Revisado há over 3 years

Pustaj M. · Revisado há over 3 years

Tona T. · Revisado há over 3 years

Prabhat S. · Revisado há over 3 years

Christopher K. · Revisado há over 3 years

GABRIELE D. · Revisado há over 3 years

Got further - but privalidge pod created without an error.

Scott W. · Revisado há over 3 years

Srinivasulu T. · Revisado há over 3 years

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

Scott W. · Revisado há over 3 years

Thilak K. · Revisado há over 3 years

Suraj Y. · Revisado há over 3 years

Nilesh P. · Revisado há over 3 years

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

Kin L. · Revisado há over 3 years

Joel A. · Revisado há over 3 years

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. · Revisado há over 3 years