Renforcer la sécurité des configurations par défaut des clusters GKE avis

Renforcer la sécurité des configurations par défaut des clusters GKE avis

9537 avis

The code for the more restrictive policy in step 7 didn't work properly

Daniel T. · Examiné il y a 10 mois

Ravishanker A. · Examiné il y a 10 mois

Ariel F. · Examiné il y a 10 mois

Step 7 error. --cluster-version 1.21.14-gke.18100 option helped.

Srikant D. · Examiné il y a 10 mois

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. · Examiné il y a 10 mois

outdate version k8s

Duy H. · Examiné il y a 10 mois

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. · Examiné il y a 10 mois

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. · Examiné il y a 10 mois

Andrei G. · Examiné il y a 10 mois

outdate

Duy H. · Examiné il y a 10 mois

Denis M. · Examiné il y a 10 mois

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. · Examiné il y a 10 mois

Step 7 error.

Srikant D. · Examiné il y a 10 mois

Krzysztof A. · Examiné il y a 10 mois

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. · Examiné il y a 10 mois

Ravishanker A. · Examiné il y a 10 mois

Ravishanker A. · Examiné il y a 10 mois

Lab instruction is not up-to-date. I wasn't able to complete Tasks 6 & 7 because PodSecurityPolicy was removed

Maciej K. · Examiné il y a 10 mois

Task 7 does not work

Vaska K. · Examiné il y a 10 mois

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. · Examiné il y a 10 mois

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. · Examiné il y a 10 mois

Pranav K. · Examiné il y a 10 mois

Sachinder Y. · Examiné il y a 10 mois

Sachinder Y. · Examiné il y a 10 mois

error at 7th tasks no CDR no psp apply Because Kubernetes remove PSP in 1.25+

Jacky N. · Examiné il y a 10 mois

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.