Hardening Default GKE Cluster Configurations Reviews
10912 reviews
Christian V. · Reviewed about 2 years ago
Ashish K. · Reviewed about 2 years ago
anil k. · Reviewed about 2 years ago
Now worked everything as supposed
Daniel T. · Reviewed about 2 years ago
Marouene D. · Reviewed about 2 years ago
Tamilselvi R. · Reviewed about 2 years ago
Good
Yuvaraj N. · Reviewed about 2 years ago
The code for the more restrictive policy in step 7 didn't work properly
Daniel T. · Reviewed about 2 years ago
Ravishanker A. · Reviewed about 2 years ago
Ariel F. · Reviewed about 2 years ago
Step 7 error. --cluster-version 1.21.14-gke.18100 option helped.
Srikant D. · Reviewed about 2 years ago
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. · Reviewed about 2 years ago
outdate version k8s
Duy H. · Reviewed about 2 years ago
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. · Reviewed about 2 years ago
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. · Reviewed about 2 years ago
Andrei G. · Reviewed about 2 years ago
outdate
Duy H. · Reviewed about 2 years ago
Denis M. · Reviewed about 2 years ago
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. · Reviewed about 2 years ago
Step 7 error.
Srikant D. · Reviewed about 2 years ago
Krzysztof A. · Reviewed about 2 years ago
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. · Reviewed about 2 years ago
Ravishanker A. · Reviewed about 2 years ago
Ravishanker A. · Reviewed about 2 years ago
Lab instruction is not up-to-date. I wasn't able to complete Tasks 6 & 7 because PodSecurityPolicy was removed
Maciej K. · Reviewed about 2 years ago
We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.