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

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

Manuel F. · Revisado há almost 3 years

ELISA M. · Revisado há almost 3 years

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

DAVID A. · Revisado há almost 3 years

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

ALEJANDRO M. · Revisado há almost 3 years

Ruben A. · Revisado há almost 3 years

EMMA B. · Revisado há almost 3 years

Chloe B. · Revisado há almost 3 years

Jose Carlos S. · Revisado há almost 3 years

Paul Nicolas K. · Revisado há almost 3 years

Renato S. · Revisado há almost 3 years

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

David P. · Revisado há about 3 years

Siddhesh N. · Revisado há about 3 years

srinu l. · Revisado há about 3 years

srinu l. · Revisado há about 3 years

Labs having some issue

Suresh M. · Revisado há about 3 years

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

Takato H. · Revisado há about 3 years

CHAKRAVARTHI M. · Revisado há about 3 years

CHAKRAVARTHI M. · Revisado há about 3 years

srinu l. · Revisado há about 3 years

Antanas L. · Revisado há about 3 years

Some steps are outdated

Shajeeb T. · Revisado há about 3 years

Kalpesh P. · Revisado há 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. · Revisado há about 3 years

Eric B. · Revisado há about 3 years