Hardening Default GKE Cluster Configurations Reviews

Jenny Adriana J. · Reviewed 11 months ago

Mykhailo S. · Reviewed 11 months ago

William L. · Reviewed 11 months ago

Prasanth S. · Reviewed 11 months ago

Vasavi R. · Reviewed 11 months ago

Christian V. · Reviewed 11 months ago

Christian V. · Reviewed 11 months ago

Ashish K. · Reviewed 11 months ago

anil k. · Reviewed 11 months ago

Now worked everything as supposed

Daniel T. · Reviewed 11 months ago

Marouene D. · Reviewed 11 months ago

Tamilselvi R. · Reviewed 11 months ago

Good

Yuvaraj N. · Reviewed 11 months ago

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

Daniel T. · Reviewed 11 months ago

Ravishanker A. · Reviewed 11 months ago

Ariel F. · Reviewed 11 months ago

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

Srikant D. · Reviewed 11 months 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 11 months ago

outdate version k8s

Duy H. · Reviewed 11 months 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 11 months 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 11 months ago

Andrei G. · Reviewed 11 months ago

outdate

Duy H. · Reviewed 11 months ago

Denis M. · Reviewed 11 months 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 12 months ago