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

Pravesh N. · 评论11 months之前

Ben G. · 评论11 months之前

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之前