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

    Hardening Default GKE Cluster Configurations Reviews

    10079 reviews

    Andreas P. · Reviewed over 1 year ago

    gg

    Yongky Budi S. · Reviewed over 1 year ago

    niks i. · Reviewed over 1 year ago

    gke version must be < 1.25

    wira d. · Reviewed over 1 year ago

    Eben S. · Reviewed over 1 year ago

    Arnanda N. · Reviewed over 1 year ago

    Wahyu L. · Reviewed over 1 year ago

    Andres F P. · Reviewed over 1 year ago

    Tiber Raniar Inner B. · Reviewed over 1 year ago

    fadli d. · Reviewed over 1 year ago

    Joy G. · Reviewed over 1 year ago

    Madeleine Jose J. · Reviewed over 1 year ago

    error in task 7

    Alif M. · Reviewed over 1 year ago

    Noval A. · Reviewed over 1 year ago

    Qolandar A. · Reviewed over 1 year ago

    Alif M. · Reviewed over 1 year ago

    thanks bug fixing

    Mohamad F. · Reviewed over 1 year ago

    Ahmad F. · Reviewed over 1 year ago

    Aldi B. · Reviewed over 1 year ago

    Joy G. · Reviewed over 1 year ago

    it's look like PodSecurityPolicy was removed in Kubernetes cluster v1.25+ and we can't continue task 7 point 2 because got error error resource mapping not found for name: "restrictive-psp" namespace: "" from "STDIN": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1". But I think we can handled it by by specify the version of cluster under v1.25+. Ex. gcloud container clusters create simplecluster --zone $MY_ZONE --cluster-version 1.21.14-gke.18100 --num-nodes 2 --metadata=disable-legacy-endpoints=false.

    Winda S. · Reviewed over 1 year ago

    Winda S. · Reviewed over 1 year ago

    Zalas H. · Reviewed over 1 year ago

    doni r. · Reviewed over 1 year ago

    Mayang S. · 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.