Protezione di Google Kubernetes Engine con Cloud IAM e i criteri di sicurezza dei pod recensioni

Yan H. · Recensione inserita circa 3 anni fa

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. · Recensione inserita circa 3 anni fa

Nikita K. · Recensione inserita circa 3 anni fa

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. · Recensione inserita circa 3 anni fa

Fabian S. · Recensione inserita circa 3 anni fa

M K. · Recensione inserita circa 3 anni fa

Namrata R. · Recensione inserita circa 3 anni fa

André Luis M. · Recensione inserita circa 3 anni fa

Aditya O. · Recensione inserita circa 3 anni fa

Great Learning

Bhushan P. · Recensione inserita circa 3 anni fa

Sneha M. · Recensione inserita circa 3 anni fa

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

Sergei A. · Recensione inserita circa 3 anni fa

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

Prudvi Kumar Reddy K. · Recensione inserita circa 3 anni fa

Akshay J. · Recensione inserita circa 3 anni fa

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. · Recensione inserita circa 3 anni fa

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

Vishal S. · Recensione inserita circa 3 anni fa

Shital P. · Recensione inserita circa 3 anni fa

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. · Recensione inserita circa 3 anni fa

Alessandro L. · Recensione inserita circa 3 anni fa

Валентин К. · Recensione inserita circa 3 anni fa

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

Олександр Г. · Recensione inserita circa 3 anni fa

Tobias A. · Recensione inserita circa 3 anni fa

Hammad A. · Recensione inserita circa 3 anni fa

Sudheer M. · Recensione inserita circa 3 anni fa

Manohar G. · Recensione inserita circa 3 anni fa