关于“Securing Google Kubernetes Engine with Cloud IAM and Pod Security Policies”的评价
12300 条评价
이다영_5087 G. · 已于 almost 3 years前审核
이다영_5087 G. · 已于 almost 3 years前审核
occured a error at restricted-psp.yaml
boram h. · 已于 almost 3 years前审核
지영 송. · 已于 almost 3 years前审核
error occured
병용 유. · 已于 almost 3 years前审核
not working
용희 권. · 已于 almost 3 years前审核
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. · 已于 almost 3 years前审核
이 주. · 已于 almost 3 years前审核
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. · 已于 almost 3 years前审核
현석 K. · 已于 almost 3 years前审核
Yeji G. · 已于 almost 3 years前审核
Yeji G. · 已于 almost 3 years前审核
병현 정. · 已于 almost 3 years前审核
Laxmi S. · 已于 almost 3 years前审核
https://cloud.google.com/kubernetes-engine/docs/deprecations/podsecuritypolicy PodSecurityのサポートはKubernetes 1.25で終わっているため、2問目以降の課題は対応できない
伊藤 徳. · 已于 almost 3 years前审核
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. · 已于 almost 3 years前审核
정승 문. · 已于 almost 3 years前审核
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. · 已于 almost 3 years前审核
not support podsecuritypolicy
jinchul j. · 已于 almost 3 years前审核
https://cloud.google.com/kubernetes-engine/docs/deprecations/podsecuritypolicy PodSecurityのサポートはKubernetes 1.25で終わっているため、2問目以降の課題は対応できない
伊藤 徳. · 已于 almost 3 years前审核
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 을 선택하도록 안내가 되었으면 좋겠습니다.
연세 김. · 已于 almost 3 years前审核
Kubernetes version must be set to 1.25 or lower to proceed normally
Haram P. · 已于 almost 3 years前审核
kubectl apply -f restricted-psp.yaml 로 pod 보안 정책 배포 시, no matches for kind "PodSecurityPolicy" in version "policy/v1beta1". k8s 홈페이지에 따르면 PodSecurityPolicy는 1.25부터 제거되었으며, GKE에서 제공하는 최소버전은 1.26 이라 진행할 수 없습니다.
연세 김. · 已于 almost 3 years前审核
Ranjeet T. · 已于 almost 3 years前审核
Adam D. · 已于 almost 3 years前审核
我们无法确保发布的评价来自已购买或已使用产品的消费者。评价未经 Google 核实。