关于“Securing Google Kubernetes Engine with Cloud IAM and Pod Security Policies”的评价

Vignesh S S Sai Ramakrishna K. · 已于 over 3 years前审核

Rajesh K. · 已于 over 3 years前审核

Cássio V. · 已于 over 3 years前审核

DineshKumar V. · 已于 over 3 years前审核

Atul M. · 已于 over 3 years前审核

Satya M. · 已于 over 3 years前审核

Satisfied

Pavani B. · 已于 over 3 years前审核

Srikala P. · 已于 over 3 years前审核

Subrahmanyasaiakhil V. · 已于 over 3 years前审核

Aabhash M. · 已于 over 3 years前审核

Jainam S. · 已于 over 3 years前审核

Pustaj M. · 已于 over 3 years前审核

Tona T. · 已于 over 3 years前审核

Prabhat S. · 已于 over 3 years前审核

Christopher K. · 已于 over 3 years前审核

GABRIELE D. · 已于 over 3 years前审核

Got further - but privalidge pod created without an error.

Scott W. · 已于 over 3 years前审核

Srinivasulu T. · 已于 over 3 years前审核

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

Scott W. · 已于 over 3 years前审核

Thilak K. · 已于 over 3 years前审核

Suraj Y. · 已于 over 3 years前审核

Nilesh P. · 已于 over 3 years前审核

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

Kin L. · 已于 over 3 years前审核

Joel A. · 已于 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. · 已于 over 3 years前审核