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

This lab is obsolete. 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 Default change: During creation of nodepools or autoscaling configuration changes for cluster versions greater than 1.24.1-gke.800 a default location policy is applied. For Spot and PVM it defaults to ANY, and for all other VM kinds a BALANCED policy is used. To change the default values use the `--location-policy` flag. ERROR: (gcloud.beta.container.clusters.update) INVALID_ARGUMENT: Pod Security Policy was removed from GKE clusters with version >= 1.25.0. The cluster cannot be created with Pod Security Policy is enabled. Instructions for using an alternative pod-level security policies can be found at: https://cloud.google.com/kubernetes-engine/docs/how-to/migrate-podsecuritypolicy.

Robert K. · 已于 almost 3 years前审核

Manuel F. · 已于 almost 3 years前审核

ELISA M. · 已于 almost 3 years前审核

There is an step that does not allow to continue due to the version of the cluster

DAVID A. · 已于 almost 3 years前审核

The content is outdated, no one has checked if the tasks could be done correctly before starting the course.

ALEJANDRO M. · 已于 almost 3 years前审核

Ruben A. · 已于 almost 3 years前审核

EMMA B. · 已于 almost 3 years前审核

Chloe B. · 已于 almost 3 years前审核

Jose Carlos S. · 已于 almost 3 years前审核

Paul Nicolas K. · 已于 almost 3 years前审核

Renato S. · 已于 almost 3 years前审核

This lab seems to be deprecated. https://cloud.google.com/kubernetes-engine/docs/deprecations/podsecuritypolicy

David P. · 已于 almost 3 years前审核

Siddhesh N. · 已于 about 3 years前审核

srinu l. · 已于 about 3 years前审核

srinu l. · 已于 about 3 years前审核

Labs having some issue

Suresh M. · 已于 about 3 years前审核

現時点では非推奨であるPodSecurityPolicyを利用している

Takato H. · 已于 about 3 years前审核

CHAKRAVARTHI M. · 已于 about 3 years前审核

CHAKRAVARTHI M. · 已于 about 3 years前审核

srinu l. · 已于 about 3 years前审核

Antanas L. · 已于 about 3 years前审核

Some steps are outdated

Shajeeb T. · 已于 about 3 years前审核

Kalpesh P. · 已于 about 3 years前审核

Lab fails here: To create the pod security policy, execute the following command: kubectl apply -f restricted-psp.yaml Copied! This policy has no effect until a cluster role is created and bound to a user or service account with the permission to use the policy. To confirm that the pod security policy has been created, execute the following command: kubectl get podsecuritypolicy restricted-psp

Eric B. · 已于 about 3 years前审核

Eric B. · 已于 about 3 years前审核