Hardening Default GKE Cluster Configurations Reviews
9536 reviews
Can not work for PodSecurityPolicy
Stephen W. · Reviewed 10 months ago
Jenny Adriana J. · Reviewed 10 months ago
Yudha P. · Reviewed 10 months ago
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
Farhan K. · Reviewed 10 months ago
Helmy T. · Reviewed 10 months ago
CC23-0272 A. · Reviewed 10 months ago
Gina M. · Reviewed 10 months ago
Mukhlas A. · Reviewed 10 months ago
ayu a. · Reviewed 10 months ago
Putra H. · Reviewed 10 months ago
Egi Putra R. · Reviewed 10 months ago
Putra H. · Reviewed 10 months ago
Nobel T. · Reviewed 10 months ago
Dzikri M. · Reviewed 10 months ago
Luthfi S. · Reviewed 10 months ago
Agung P. · Reviewed 10 months ago
Ida Putu Sucita D. · Reviewed 10 months ago
I'm stuck in task 7.2
Ida Putu Sucita D. · Reviewed 10 months ago
Khofidin O. · Reviewed 10 months ago
Robby R. · Reviewed 10 months ago
Black M. · Reviewed 10 months ago
Yh. N. · Reviewed 10 months ago
Nobel T. · Reviewed 10 months ago
The cluster created in the lab is of version 1.25, where PodSecurityPolicy has been depreceated. Thus the lab does not work from Task 7 onwards. It is possible to circumvent this for now by using "--release-channel=stable" which will create a cluster of version 1.24. It would be better to change the lab to use Pod Security Admission.
Esko R. · Reviewed 10 months ago
This lab hasn't been updated because psp is already deprecated by kubernetes but still used in this lab
Setia K. · Reviewed 10 months ago
We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.