Hardening Default GKE Cluster Configurations recensioni
16614 recensioni
The code for the more restrictive policy in step 7 didn't work properly
Daniel T. · Recensione inserita quasi 3 anni fa
Ravishanker A. · Recensione inserita quasi 3 anni fa
Ariel F. · Recensione inserita quasi 3 anni fa
Step 7 error. --cluster-version 1.21.14-gke.18100 option helped.
Srikant D. · Recensione inserita quasi 3 anni fa
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. · Recensione inserita quasi 3 anni fa
outdate version k8s
Duy H. · Recensione inserita quasi 3 anni fa
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. · Recensione inserita quasi 3 anni fa
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. · Recensione inserita quasi 3 anni fa
Andrei G. · Recensione inserita quasi 3 anni fa
outdate
Duy H. · Recensione inserita quasi 3 anni fa
Denis M. · Recensione inserita quasi 3 anni fa
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. · Recensione inserita quasi 3 anni fa
Step 7 error.
Srikant D. · Recensione inserita quasi 3 anni fa
Krzysztof A. · Recensione inserita quasi 3 anni fa
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. · Recensione inserita quasi 3 anni fa
Ravishanker A. · Recensione inserita quasi 3 anni fa
Ravishanker A. · Recensione inserita quasi 3 anni fa
Lab instruction is not up-to-date. I wasn't able to complete Tasks 6 & 7 because PodSecurityPolicy was removed
Maciej K. · Recensione inserita quasi 3 anni fa
Task 7 does not work
Vaska K. · Recensione inserita quasi 3 anni fa
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. · Recensione inserita quasi 3 anni fa
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. · Recensione inserita quasi 3 anni fa
Pranav K. · Recensione inserita quasi 3 anni fa
Sachinder Y. · Recensione inserita quasi 3 anni fa
Sachinder Y. · Recensione inserita quasi 3 anni fa
error at 7th tasks no CDR no psp apply Because Kubernetes remove PSP in 1.25+
Jacky N. · Recensione inserita quasi 3 anni fa
Non garantiamo che le recensioni pubblicate provengano da consumatori che hanno acquistato o utilizzato i prodotti. Le recensioni non sono verificate da Google.