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

이다영_5087 G. · Vor fast 3 Jahre überprüft

occured a error at restricted-psp.yaml

boram h. · Vor fast 3 Jahre überprüft

지영 송. · Vor fast 3 Jahre überprüft

error occured

병용 유. · Vor fast 3 Jahre überprüft

not working

용희 권. · Vor fast 3 Jahre überprüft

PodSecurityPolicy was deprecated in Kubernetes v1.21, and removed from Kubernetes in v1.25. and replaced with Pod Security Admission so part 2 of this lab cant be completed!

Per Daniel S. · Vor fast 3 Jahre überprüft

이 주. · Vor fast 3 Jahre überprüft

1. The check failed even though the serviceAccountUser role was granted to username 2. 2. Since PodSecurityPolicy has been completely deprecated since version 1.25, when kubectl apply -f restricted-psp.yaml is executed, the following error appears and the task does not proceed. 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

Soonwoo K. · Vor fast 3 Jahre überprüft

현석 K. · Vor fast 3 Jahre überprüft

Yeji G. · Vor fast 3 Jahre überprüft

병현 정. · Vor fast 3 Jahre überprüft

Laxmi S. · Vor fast 3 Jahre überprüft

https://cloud.google.com/kubernetes-engine/docs/deprecations/podsecuritypolicy PodSecurityのサポートはKubernetes 1.25で終わっているため、2問目以降の課題は対応できない

伊藤徳. · Vor fast 3 Jahre überprüft

helm error when creating PSP error: resource mapping not found for name: no matches for kind "PodSecurityPolicy" in version "policy/v1" ensure CRDs are installed first

Patrick W. · Vor fast 3 Jahre überprüft

정승 문. · Vor fast 3 Jahre überprüft

1. The check failed even though the serviceAccountUser role was granted to username 2. 2. Since PodSecurityPolicy has been completely deprecated since version 1.25, when kubectl apply -f restricted-psp.yaml is executed, the following error appears and the task does not proceed. 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

Soonwoo K. · Vor fast 3 Jahre überprüft

not support podsecuritypolicy

jinchul j. · Vor fast 3 Jahre überprüft

https://cloud.google.com/kubernetes-engine/docs/deprecations/podsecuritypolicy PodSecurityのサポートはKubernetes 1.25で終わっているため、2問目以降の課題は対応できない

伊藤徳. · Vor fast 3 Jahre überprüft

kubectl apply -f restricted-psp.yaml 로 pod 보안 정책 배포 시, no matches for kind "PodSecurityPolicy" in version "policy/v1beta1". k8s 홈페이지에 따르면 PodSecurityPolicy는 1.25부터 제거되었으며, GKE에서 제공하는 최소버전은 1.26 이라 진행할 수 없습니다. Release Channel 대신 Static version 을 선택하도록 안내가 되었으면 좋겠습니다.

연세 김. · Vor fast 3 Jahre überprüft

Kubernetes version must be set to 1.25 or lower to proceed normally

Haram P. · Vor fast 3 Jahre überprüft

kubectl apply -f restricted-psp.yaml 로 pod 보안 정책 배포 시, no matches for kind "PodSecurityPolicy" in version "policy/v1beta1". k8s 홈페이지에 따르면 PodSecurityPolicy는 1.25부터 제거되었으며, GKE에서 제공하는 최소버전은 1.26 이라 진행할 수 없습니다.

연세 김. · Vor fast 3 Jahre überprüft

Ranjeet T. · Vor fast 3 Jahre überprüft

Adam D. · Vor fast 3 Jahre überprüft