Opinie (Securing Google Kubernetes Engine with Cloud IAM and Pod Security Policies)

bad

Chakravarthy S. · Sprawdzono prawie 3 lata temu

Naohiro F. · Sprawdzono prawie 3 lata temu

Podセキュリティーポリシーが作成されない。

野崎秀人野. · Sprawdzono prawie 3 lata temu

Akshay J. · Sprawdzono prawie 3 lata temu

Sergey B. · Sprawdzono prawie 3 lata temu

The material is outdated and the K8s API used here deprecated.

Sebastian G. · Sprawdzono prawie 3 lata temu

Nonaka T. · Sprawdzono prawie 3 lata temu

Tapan H. · Sprawdzono prawie 3 lata temu

Sarath Kumar M. · Sprawdzono prawie 3 lata temu

Akshay J. · Sprawdzono prawie 3 lata temu

Jason V. · Sprawdzono prawie 3 lata temu

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. For additional details, please refer to https://cloud.google.com/kubernetes-engine/docs/how-to/pod-security-policies Default change: During creation of nodepools or autoscaling configuration changes for cluster versions greater than 1.24.1-gke.800 a default location policy is applied. For Spot and PVM it defaults to ANY, and for all other VM kinds a BALANCED policy is used. To change the default values use the `--location-policy` flag. ERROR: (gcloud.beta.container.clusters.update) 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. Instructions for using an alternative pod-level security policies can be found at: https://cloud.google.com/kubernetes-engine/docs/how-to/migrate-podsecuritypolicy. - '@type': type.googleapis.com/google.rpc.RequestInfo requestId: '0xb8c0e903480f30a3'

Sivaprasath M. · Sprawdzono prawie 3 lata temu

Could not create pod security Policies: student_03_525b2bce9214@cloudshell:~/training-data-analyst/courses/ak8s/14_IAM (qwiklabs-gcp-04-732f88260d6a)$ kubectl 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"

Donglin J. · Sprawdzono prawie 3 lata temu

Jason V. · Sprawdzono prawie 3 lata temu

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. For additional details, please refer to https://cloud.google.com/kubernetes-engine/docs/how-to/pod-security-policies Default change: During creation of nodepools or autoscaling configuration changes for cluster versions greater than 1.24.1-gke.800 a default location policy is applied. For Spot and PVM it defaults to ANY, and for all other VM kinds a BALANCED policy is used. To change the default values use the `--location-policy` flag. ERROR: (gcloud.beta.container.clusters.update) 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. Instructions for using an alternative pod-level security policies can be found at: https://cloud.google.com/kubernetes-engine/docs/how-to/migrate-podsecuritypolicy. - '@type': type.googleapis.com/google.rpc.RequestInfo requestId: '0xb8c0e903480f30a3'

Sivaprasath M. · Sprawdzono prawie 3 lata temu

Lab does not work

John M. · Sprawdzono prawie 3 lata temu

no matches for kind "PodSecurityPolicy" in version "policy/v1beta1. - failed could not create security policy had to move on

Peter G. · Sprawdzono prawie 3 lata temu

Scot B. · Sprawdzono prawie 3 lata temu

Gandhi S. · Sprawdzono prawie 3 lata temu

There is an error in this lab due to deprecated PodSecurityPolicy and it could not be finished.

Anthony R. · Sprawdzono prawie 3 lata temu

pod security creation coudl not happen with all steps mentioned

Divya A. · Sprawdzono prawie 3 lata temu

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 apiVersion: policy/v1beta1 kind: PodSecurityPolicy metadata: name: restricted-psp spec: privileged: false # Don't allow privileged pods! seLinux: rule: RunAsAny supplementalGroups: rule: RunAsAny runAsUser: rule: MustRunAsNonRoot fsGroup: rule: RunAsAny volumes: - '*'

Esmeralda S. · Sprawdzono prawie 3 lata temu

pod security creation coudl not happen with all steps mentioned

Divya A. · Sprawdzono prawie 3 lata temu