Hardening Default GKE Cluster Configurations avis
10925 avis
mahes s. · Examiné il y a environ 2 ans
Erwin M. · Examiné il y a environ 2 ans
ERROR TASK 7
Akmal M. · Examiné il y a environ 2 ans
Wahyu A. · Examiné il y a environ 2 ans
error trying to implement Task 7.....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
Oluwafemi A. · Examiné il y a environ 2 ans
Mukhlas A. · Examiné il y a environ 2 ans
Alvin .. · Examiné il y a environ 2 ans
PodSecurityPolicy was removed in Kubernetes cluster v1.25+ and we can't continue task 7 point 2. But we can solve it by specify the version of cluster under v1.25. For an example: gcloud container clusters create simplecluster --zone $MY_ZONE --cluster-version 1.21.14-gke.18100 --num-nodes 2 --metadata=disable-legacy-endpoints=false
Adhi P. · Examiné il y a environ 2 ans
Maulana Akbar D. · Examiné il y a environ 2 ans
Adhi P. · Examiné il y a environ 2 ans
Error in Task 7, 2 - 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 Fix: Use cluster version 1.21 gcloud container clusters create simplecluster --zone $MY_ZONE --cluster-version 1.21.14-gke.18100 --num-nodes 2 --metadata=disable-legacy-endpoints=false
Shams H. K. · Examiné il y a environ 2 ans
Error in Task 7, 2 - 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
Shams H. K. · Examiné il y a environ 2 ans
Erick C. · Examiné il y a environ 2 ans
Reihan S. · Examiné il y a environ 2 ans
Reihan S. · Examiné il y a environ 2 ans
AGENG P. · Examiné il y a environ 2 ans
Unable to finish the lab due to depreciation on psp in new version of GKE
Achille M. · Examiné il y a environ 2 ans
In this version, podsecuritypolicy and policy/v1beta1 are deprecated and not's possible to complete the lab: 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 Solved setting the --cluster-version flag to 1.21
Adrian C. · Examiné il y a environ 2 ans
In this version, podsecuritypolicy and policy/v1beta1 are deprecated and not's possible to complete the lab: 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
Adrian C. · Examiné il y a environ 2 ans
Unable to finish the lab due to depreciation on psp in new version of GKE
Achille M. · Examiné il y a environ 2 ans
Andre R. · Examiné il y a environ 2 ans
Gregorius S. · Examiné il y a environ 2 ans
Oluwafemi A. · Examiné il y a environ 2 ans
Command to create podsecurity is not working. So lab failed and I wasted time.
Frank E. · Examiné il y a environ 2 ans
Anand K. · Examiné il y a environ 2 ans
Nous ne pouvons pas certifier que les avis publiés proviennent de consommateurs qui ont acheté ou utilisé les produits. Les avis ne sont pas vérifiés par Google.