Hardening Default GKE Cluster Configurations Reviews
Loading...
No results found.

    Hardening Default GKE Cluster Configurations Reviews

    10085 reviews

    Ariel F. · Reviewed over 1 year ago

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

    Srikant D. · Reviewed over 1 year 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 over 1 year ago

    outdate version k8s

    Duy H. · Reviewed over 1 year 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 over 1 year 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 over 1 year ago

    Andrei G. · Reviewed over 1 year ago

    outdate

    Duy H. · Reviewed over 1 year ago

    Denis M. · Reviewed over 1 year 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 over 1 year ago

    Step 7 error.

    Srikant D. · Reviewed over 1 year ago

    Krzysztof A. · Reviewed over 1 year 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 over 1 year ago

    Ravishanker A. · Reviewed over 1 year ago

    Ravishanker A. · Reviewed over 1 year ago

    Lab instruction is not up-to-date. I wasn't able to complete Tasks 6 & 7 because PodSecurityPolicy was removed

    Maciej K. · Reviewed over 1 year ago

    Task 7 does not work

    Vaska K. · Reviewed over 1 year 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 over 1 year 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

    Yulius E. · Reviewed over 1 year ago

    Pranav K. · Reviewed over 1 year ago

    Sachinder Y. · Reviewed over 1 year ago

    Sachinder Y. · Reviewed over 1 year ago

    error at 7th tasks no CDR no psp apply Because Kubernetes remove PSP in 1.25+

    Jacky N. · Reviewed over 1 year ago

    Arrabolu Chandra Shekar R. · Reviewed over 1 year ago

    error at 7th tasks no CDR no psp apply

    Jacky N. · Reviewed over 1 year ago

    We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.