리뷰 Hardening Default GKE Cluster Configurations개
리뷰 9615개
Marouene D. · 11개월 전에 리뷰됨
Tamilselvi R. · 11개월 전에 리뷰됨
Good
Yuvaraj N. · 11개월 전에 리뷰됨
The code for the more restrictive policy in step 7 didn't work properly
Daniel T. · 11개월 전에 리뷰됨
Ravishanker A. · 11개월 전에 리뷰됨
Ariel F. · 11개월 전에 리뷰됨
Step 7 error. --cluster-version 1.21.14-gke.18100 option helped.
Srikant D. · 11개월 전에 리뷰됨
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.
Andrii K. · 11개월 전에 리뷰됨
outdate version k8s
Duy H. · 11개월 전에 리뷰됨
outdated lab, create cluster in first step: gcloud container clusters create simplecluster --zone $MY_ZONE --num-nodes 2 --metadata=disable-legacy-endpoints=false --cluster-version=1.21.14-gke.18800 --no-enable-autoupgrade
Denis M. · 11개월 전에 리뷰됨
Steps 6 & 7 cannot be implemented: error: resource mapping not found for name: "restrictive-psp" namespace: "" from "STDIN": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1" ensure CRDs are installed first
Andrei G. · 11개월 전에 리뷰됨
Andrei G. · 11개월 전에 리뷰됨
outdate
Duy H. · 11개월 전에 리뷰됨
Denis M. · 11개월 전에 리뷰됨
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. This lab uses v1.25 hence unable to use pod security preventing me from completing the lab
Oluseyi S. · 11개월 전에 리뷰됨
Step 7 error.
Srikant D. · 11개월 전에 리뷰됨
Krzysztof A. · 11개월 전에 리뷰됨
error: resource mapping not found for name: "restrictive-psp" namespace: "" from "STDIN": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1" ensure CRDs are installed first >>> the solution is : gcloud container clusters create simplecluster --zone $MY_ZONE --num-nodes 2 --metadata=disable-legacy-endpoints=false --cluster-version=1.21.14-gke.18800 --no-enable-autoupgrade
Félix V. · 11개월 전에 리뷰됨
Ravishanker A. · 11개월 전에 리뷰됨
Ravishanker A. · 11개월 전에 리뷰됨
Lab instruction is not up-to-date. I wasn't able to complete Tasks 6 & 7 because PodSecurityPolicy was removed
Maciej K. · 11개월 전에 리뷰됨
Task 7 does not work
Vaska K. · 11개월 전에 리뷰됨
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. This lab uses v1.25 hence unable to use pod security preventing me from completing the lab
Oluseyi S. · 11개월 전에 리뷰됨
error: resource mapping not found for name: restrictive-psp namespace: from STDIN: no matches for kind PodSecurityPolicy in version policy/v1beta1 ensure CRDs are installed first
Yulius E. · 11개월 전에 리뷰됨
Pranav K. · 11개월 전에 리뷰됨
Google은 게시된 리뷰가 제품을 구매 또는 사용한 소비자에 의해 작성되었음을 보증하지 않습니다. 리뷰는 Google의 인증을 거치지 않습니다.