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

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. · Reviewed almost 3 years ago

Manuel F. · Reviewed almost 3 years ago

ELISA M. · Reviewed almost 3 years ago

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

DAVID A. · Reviewed almost 3 years ago

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

ALEJANDRO M. · Reviewed almost 3 years ago

Ruben A. · Reviewed almost 3 years ago

EMMA B. · Reviewed almost 3 years ago

Chloe B. · Reviewed almost 3 years ago

Jose Carlos S. · Reviewed almost 3 years ago

Paul Nicolas K. · Reviewed almost 3 years ago

Renato S. · Reviewed almost 3 years ago

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

David P. · Reviewed almost 3 years ago

Siddhesh N. · Reviewed about 3 years ago

srinu l. · Reviewed about 3 years ago

srinu l. · Reviewed about 3 years ago

Labs having some issue

Suresh M. · Reviewed about 3 years ago

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

Takato H. · Reviewed about 3 years ago

CHAKRAVARTHI M. · Reviewed about 3 years ago

CHAKRAVARTHI M. · Reviewed about 3 years ago

srinu l. · Reviewed about 3 years ago

Antanas L. · Reviewed about 3 years ago

Some steps are outdated

Shajeeb T. · Reviewed about 3 years ago

Kalpesh P. · Reviewed about 3 years ago

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. · Reviewed about 3 years ago

Eric B. · Reviewed about 3 years ago