Securing Google Kubernetes Engine with Cloud IAM and Pod Security Policies Reviews
12300 reviews
Yan H. · Reviewed около 3 лет ago
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. · Reviewed около 3 лет ago
Nikita K. · Reviewed около 3 лет ago
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. · Reviewed около 3 лет ago
Fabian S. · Reviewed около 3 лет ago
M K. · Reviewed около 3 лет ago
Namrata R. · Reviewed около 3 лет ago
André Luis M. · Reviewed около 3 лет ago
Aditya O. · Reviewed около 3 лет ago
Great Learning
Bhushan P. · Reviewed около 3 лет ago
Sneha M. · Reviewed около 3 лет ago
Pod Security Policy removed from version 1.25. The lab doesn't work.
Sergei A. · Reviewed около 3 лет ago
restricted-psp is showing error for not having a resource mapping in the YAML script
Prudvi Kumar Reddy K. · Reviewed около 3 лет ago
Akshay J. · Reviewed около 3 лет ago
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. · Reviewed около 3 лет ago
There is some problem with lab. It is not progressing with first gcloud command
Vishal S. · Reviewed около 3 лет ago
Shital P. · Reviewed около 3 лет ago
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. · Reviewed около 3 лет ago
Alessandro L. · Reviewed около 3 лет ago
Валентин К. · Reviewed около 3 лет ago
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
Олександр Г. · Reviewed около 3 лет ago
Tobias A. · Reviewed около 3 лет ago
Hammad A. · Reviewed около 3 лет ago
Sudheer M. · Reviewed около 3 лет ago
Manohar G. · Reviewed около 3 лет ago
We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.