Sécuriser Google Kubernetes Engine avec des stratégies Cloud IAM et de sécurité des pods avis

Yan H. · Examiné il y a environ 3 ans

policy/v1beta1 PodSecurityPolicy is unavailable in v1.25+, which is default. Lab needs updating to newer approach. Worked around by setting older control plane version

Karl H. · Examiné il y a environ 3 ans

Nikita K. · Examiné il y a environ 3 ans

policy/v1beta1 PodSecurityPolicy is deprecated in the default kubernetes version that is applied when you create the cluster. I had to re-create the cluster with a static version <1.25 in order to complete the lab. Everything else is fine

Sam D. · Examiné il y a environ 3 ans

Fabian S. · Examiné il y a environ 3 ans

M K. · Examiné il y a environ 3 ans

Namrata R. · Examiné il y a environ 3 ans

André Luis M. · Examiné il y a environ 3 ans

Aditya O. · Examiné il y a environ 3 ans

Great Learning

Bhushan P. · Examiné il y a environ 3 ans

Sneha M. · Examiné il y a environ 3 ans

Pod Security Policy removed from version 1.25. The lab doesn't work.

Sergei A. · Examiné il y a environ 3 ans

restricted-psp is showing error for not having a resource mapping in the YAML script

Prudvi Kumar Reddy K. · Examiné il y a environ 3 ans

Akshay J. · Examiné il y a environ 3 ans

kubectl apply -f restricted-psp.yaml command returns error: resource mapping not found for name: "restricted-psp" namespace: "" from "restricted-psp.yaml": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1" ensure CRDs are installed first

Kseniya Z. · Examiné il y a environ 3 ans

There is some problem with lab. It is not progressing with first gcloud command

Vishal S. · Examiné il y a environ 3 ans

Shital P. · Examiné il y a environ 3 ans

getting error while deploying pod security policy ubectl apply -f restricted-psp.yaml error: resource mapping not found for name: "restricted-psp" namespace: "" from "restricted-psp.yaml": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1" ensure CRDs are installed first

Sumit G. · Examiné il y a environ 3 ans

Alessandro L. · Examiné il y a environ 3 ans

Валентин К. · Examiné il y a environ 3 ans

There is a bug when apply pod security policy: no matches for kind "PodSecurityPolicy" in version "policy/v1beta1" Issue described in https://github.com/longhorn/longhorn/issues/4569 Works well with 1.24 version

Олександр Г. · Examiné il y a environ 3 ans

Tobias A. · Examiné il y a environ 3 ans

Hammad A. · Examiné il y a environ 3 ans

Sudheer M. · Examiné il y a environ 3 ans

Manohar G. · Examiné il y a environ 3 ans