Hardening Default GKE Cluster Configurations Reviews

Can not work for PodSecurityPolicy

Stephen W. · Reviewed about 2 years ago

Can not work for PodSecurityPolicy

Stephen W. · Reviewed about 2 years ago

Jenny Adriana J. · Reviewed about 2 years ago

Yudha P. · Reviewed about 2 years 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 about 2 years ago

Helmy T. · Reviewed about 2 years ago

CC23-0272 A. · Reviewed about 2 years ago

Gina M. · Reviewed about 2 years ago

Mukhlas A. · Reviewed about 2 years ago

ayu a. · Reviewed about 2 years ago

Putra H. · Reviewed about 2 years ago

Egi Putra R. · Reviewed about 2 years ago

Putra H. · Reviewed about 2 years ago

Nobel T. · Reviewed about 2 years ago

Dzikri M. · Reviewed about 2 years ago

Luthfi S. · Reviewed about 2 years ago

Agung P. · Reviewed about 2 years ago

Ida Putu Sucita D. · Reviewed about 2 years ago

I'm stuck in task 7.2

Ida Putu Sucita D. · Reviewed about 2 years ago

Khofidin O. · Reviewed about 2 years ago

Robby R. · Reviewed about 2 years ago

Black M. · Reviewed about 2 years ago

Yh. N. · Reviewed about 2 years ago

Nobel T. · Reviewed about 2 years 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 about 2 years ago