关于“Hardening Default GKE Cluster Configurations”的评价

Step 3 no longer works as the default image has been hardened to no longer allow you to mount the root filesystem

Ben G. · 已于 11 months前审核

loc n. · 已于 11 months前审核

Jenny Adriana J. · 已于 11 months前审核

Mykhailo S. · 已于 11 months前审核

William L. · 已于 11 months前审核

Prasanth S. · 已于 11 months前审核

Vasavi R. · 已于 11 months前审核

Christian V. · 已于 11 months前审核

Christian V. · 已于 11 months前审核

Ashish K. · 已于 11 months前审核

anil k. · 已于 11 months前审核

Now worked everything as supposed

Daniel T. · 已于 11 months前审核

Marouene D. · 已于 11 months前审核

Tamilselvi R. · 已于 11 months前审核

Good

Yuvaraj N. · 已于 11 months前审核

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

Daniel T. · 已于 11 months前审核

Ravishanker A. · 已于 11 months前审核

Ariel F. · 已于 11 months前审核

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

Srikant D. · 已于 11 months前审核

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. · 已于 11 months前审核

outdate version k8s

Duy H. · 已于 11 months前审核

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. · 已于 11 months前审核

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. · 已于 11 months前审核

Andrei G. · 已于 11 months前审核

outdate

Duy H. · 已于 11 months前审核