关于“Hardening Default GKE Cluster Configurations”的评价
正在加载…
未找到任何结果。

在 Google Cloud 控制台中运用您的技能

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

评论

Ariel F. · 评论over 2 years之前

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

Srikant D. · 评论over 2 years之前

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. · 评论over 2 years之前

outdate version k8s

Duy H. · 评论over 2 years之前

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. · 评论over 2 years之前

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. · 评论over 2 years之前

Andrei G. · 评论over 2 years之前

outdate

Duy H. · 评论over 2 years之前

Denis M. · 评论over 2 years之前

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. · 评论over 2 years之前

Step 7 error.

Srikant D. · 评论over 2 years之前

Krzysztof A. · 评论over 2 years之前

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. · 评论over 2 years之前

Ravishanker A. · 评论over 2 years之前

Ravishanker A. · 评论over 2 years之前

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

Maciej K. · 评论over 2 years之前

Task 7 does not work

Vaska K. · 评论over 2 years之前

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. · 评论over 2 years之前

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. · 评论over 2 years之前

Pranav K. · 评论over 2 years之前

Sachinder Y. · 评论over 2 years之前

Sachinder Y. · 评论over 2 years之前

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

Jacky N. · 评论over 2 years之前

Arrabolu Chandra Shekar R. · 评论over 2 years之前

error at 7th tasks no CDR no psp apply

Jacky N. · 评论over 2 years之前

我们无法确保发布的评价来自已购买或已使用产品的消费者。评价未经 Google 核实。