리뷰 Cloud IAM 및 포드 보안 정책으로 Google Kubernetes Engine 보호하기개

Aashutosh T. · 2년 초과 전에 리뷰됨

Hari Krishna M. · 2년 초과 전에 리뷰됨

the lab is broken

Ignacio H. · 2년 초과 전에 리뷰됨

Carlos B. · 2년 초과 전에 리뷰됨

didn't work because psp is deprecated

Jose A. · 2년 초과 전에 리뷰됨

タスク２はクラスタを設定する際にver1.24選択して立てることでラボを進めることができました。

Hiroki T. · 2년 초과 전에 리뷰됨

The tests were good but the creation of PSP failed due to the deprecation and removal of PSP resource as from K8s v1.25. When creating the cluster, I left some fields in default as instructed, hence a v1.27 cluster was created. This version doesn't support PSP. Please update the lab content accordingly.

Zawadi O. · 2년 초과 전에 리뷰됨

The tests were good but the creation of PSP failed due to the deprecation and removal of PSP resource as from K8s v1.25. When creating the cluster, I left some fields in default as instructed, hence a v1.27 cluster was created. This version doesn't support PSP. Please update the lab content accordingly.

Zawadi O. · 2년 초과 전에 리뷰됨

The are some problems with scripts and current kubernetes release

angel C. · 2년 초과 전에 리뷰됨

タスク２が終了しません

Hiroki T. · 2년 초과 전에 리뷰됨

Hiroki T. · 2년 초과 전에 리뷰됨

Gaurav J. · 2년 초과 전에 리뷰됨

Task 2 no longer support on K8s

Alex F. · 2년 초과 전에 리뷰됨

error: resource mapping not found for name: "restricted-psp" namespace: "" from "restricted-psp.yaml": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1"

Obi A. · 2년 초과 전에 리뷰됨

no esta actualizado el laboratorio con la version de kubernetes

oscar r. · 거의 3년 전에 리뷰됨

PSPはすでに廃止されているため手順通りでは完了できず古いバージョンのクラスタで作り直して進行した。ラボ内容のアップデートが必要。

Hirofumi H. · 거의 3년 전에 리뷰됨

kubectl apply -f restricted-psp.yaml コマンド実行時 エラーにより実行できない

楠井 慧. · 거의 3년 전에 리뷰됨

I was chat with support team ,they said problem on backend so if possible provide extra attempt chances

lakshmi u. · 거의 3년 전에 리뷰됨

"Cloud IAM 및 포드 보안 정ㅂ책으로 Google Kubernetes Engine 보호하기" podsecurity정책 : GKE 버전정보가 상이해서 진행 안되는 부분 있음 1.24버전으로 진행함 [[해당 의견 참고하여 GKE생성하였더니 끝까지 마무리됨]]

종민 이. · 거의 3년 전에 리뷰됨

楠井 慧. · 거의 3년 전에 리뷰됨

Abhishek B. · 거의 3년 전에 리뷰됨

Yeo B. · 거의 3년 전에 리뷰됨

pod security creation coudl not happen with all steps mentioned

Divya A. · 거의 3년 전에 리뷰됨

bad case and not good feedback

조홍식 S. · 거의 3년 전에 리뷰됨

Troubleshooting info: Principal: student-01-2286db4df7fb@qwiklabs.net Resource: qwiklabs-gcp-02-77553bb73067 Troubleshooting URL: console.cloud.google.com/iam-admin/troubleshooter;permissions=compute.networks.list,compute.projects.get,compute.regions.list,compute.subnetworks.list,iam.serviceAccounts.get;principal=student-01-2286db4df7fb@qwiklabs.net;resources=%2F%2Fcloudresourcemanager.googleapis.com%2Fprojects%2Fqwiklabs-gcp-02-77553bb73067,%2F%2Fcloudresourcemanager.googleapis.com%2Fprojects%2Fqwiklabs-gcp-02-77553bb73067,%2F%2Fcloudresourcemanager.googleapis.com%2Fprojects%2Fqwiklabs-gcp-02-77553bb73067,%2F%2Fcloudresourcemanager.googleapis.com%2Fprojects%2Fqwiklabs-gcp-02-77553bb73067,%2F%2Fcloudresourcemanager.googleapis.com%2Fprojects%2Fqwiklabs-gcp-02-77553bb73067 Missing permissions: compute.networks.list compute.projects.get compute.regions.list compute.subnetworks.list iam.serviceAccounts.get ----------------------------------------------------------------------- tudent_01_e9864640702a@cloudshell:~/training-data-analyst/courses/ak8s/14_IAM (qwiklabs-gcp-01-4ad7d8571d6f)$ kubectl apply -f restricted-psp.yaml Unable to connect to the server: dial tcp 35.226.198.74:443: i/o timeout student_01_e9864640702a@cloudshell:~/training-data-analyst/courses/ak8s/14_IAM (qwiklabs-gcp-01-4ad7d8571d6f)$ kubectl apply -f restricted-psp.yaml The connection to the server 35.226.198.74 was refused - did you specify the right host or port? student_01_e9864640702a@cloudshell:~/training-data-analyst/courses/ak8s/14_IAM (qwiklabs-gcp-01-4ad7d8571d6f)$ kubectl apply -f restricted-psp.yaml The connection to the server 35.226.198.74 was refused - did you specify the right host or port? student_01_e9864640702a@cloudshell:~/training-data-analyst/courses/ak8s/14_IAM (qwiklabs-gcp-01-4ad7d8571d6f)$ kubectl get podsecuritypolicy restricted-psp E0806 15:42:20.773465 490 memcache.go:265] couldn't get current server API group list: Get "https://35.226.198.74/api?timeout=32s": net/http: TLS handshake timeout E0806 15:42:29.833274 490 memcache.go:265] couldn't get current server API group list: Get "https://35.226.198.74/api?timeout=32s": dial tcp 35.226.198.74:443: connect: connection refused - error from a previous attempt: read tcp 172.17.0.4:46682->35.226.198.74:443: read: connection reset by peer E0806 15:42:29.991195 490 memcache.go:265] couldn't get current server API group list: Get "https://35.226.198.74/api?timeout=32s": dial tcp 35.226.198.74:443: connect: connection refused E0806 15:42:30.148906 490 memcache.go:265] couldn't get current server API group list: Get "https://35.226.198.74/api?timeout=32s": dial tcp 35.226.198.74:443: connect: connection refused E0806 15:42:30.307272 490 memcache.go:265] couldn't get current server API group list: Get "https://35.226.198.74/api?timeout=32s": dial tcp 35.226.198.74:443: connect: connection refused The connection to the server 35.226.198.74 was refused - did you specify the right host or port?

영하 장. · 거의 3년 전에 리뷰됨