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

(전희영) L. · Examiné il y a presque 3 ans

민환 오. · Examiné il y a presque 3 ans

Brandon S. · Examiné il y a presque 3 ans

이번에는 Cluster Create 시 오류 발생해서 진행이 안되어 다시 재수행 할예정

진용 이. · Examiné il y a presque 3 ans

PoDsecuritypolicy 정책 만들때 오류가 발생합니다. no matches for kind "PodSecurityPolicy" in version "policy/v1beta1" ensure CRDs are installed first

진용 이. · Examiné il y a presque 3 ans

성훈 장. · Examiné il y a presque 3 ans

Broken. Can't apply pod security policy.

Lloyd K. · Examiné il y a presque 3 ans

Abhay G. · Examiné il y a presque 3 ans

Task 1 - Granting Permission (Service Account User) has some problems Task 2 - restricted-psp.yml has problem with pod-security-policy Unable to complete lab

Nithin K. · Examiné il y a presque 3 ans

Tatsuya O. · Examiné il y a presque 3 ans

Cannot copmpleted. Podsecuritypolicy not allowed in cluster version

Manuel S. · Examiné il y a presque 3 ans

did not work good

kineret l. · Examiné il y a presque 3 ans

Francesco R. · Examiné il y a presque 3 ans

Eric E. · Examiné il y a presque 3 ans

kineret l. · Examiné il y a presque 3 ans

Avi G. · Examiné il y a presque 3 ans

lab has some thing wrong with it with the kube versions

Saar B. · Examiné il y a presque 3 ans

BROKE LAB

Guy O. · Examiné il y a presque 3 ans

敦志 髙. · Examiné il y a presque 3 ans

Lev V. · Examiné il y a presque 3 ans

error: resource mapping not found for name: "restricted-psp" namespace: ""

Sho I. · Examiné il y a presque 3 ans

Ignacio A. · Examiné il y a presque 3 ans

student_01_a283a5f8d347@cloudshell:~/ak8s/Security (qwiklabs-gcp-00-a3a049174473)$ kubectl apply -f restricted-psp.yaml error: resource mapping not found for name: "restricted-psp" namespace: "" from "restricted-psp.yaml": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1" ensure CRDs are installed first student_01_a283a5f8d347@cloudshell:~/ak8s/Security (qwiklabs-gcp-00-a3a049174473)$ kubectl get podsecuritypolicy restricted-psp error: the server doesn't have a resource type "podsecuritypolicy" student_01_a283a5f8d347@cloudshell:~/ak8s/Security (qwiklabs-gcp-00-a3a049174473)$ gcloud beta container clusters update $my_cluster --zone $my_zone --enable-pod-security-policy 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. student_01_a283a5f8d347@cloudshell:~/ak8s/Security (qwiklabs-gcp-00-a3a049174473)$ student_01_a283a5f8d347@cloudshell:~/ak8s/Security (qwiklabs-gcp-00-a3a049174473)$ kubectl get podsecuritypolicies error: the server doesn't have a resource type "podsecuritypolicies"

康二 田. · Examiné il y a presque 3 ans

error! student_01_89b30fedca41@cloudshell:~/ak8s/Security (qwiklabs-gcp-02-0d4ed7eb32f1)$ kubectl apply -f restricted-psp.yamlerror: resource mapping not found for name: "restricted-psp" namespace: "" from "restricted-psp.yaml": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1" ensure CRDs are installed first student_01_89b30fedca41@cloudshell:~/ak8s/Security (qwiklabs-gcp-02-0d4ed7eb32f1)$ kubectl get podsecuritypolicy restricted-psp error: the server doesn't have a resource type "podsecuritypolicy"

康二 田. · Examiné il y a presque 3 ans

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

DAVID A. · Examiné il y a presque 3 ans