Securing Google Kubernetes Engine with IAM and Pod Security Admission Reviews

Binay M. · Reviewed over 1 year ago

tom y. · Reviewed over 1 year ago

jack B. · Reviewed over 1 year ago

Gabriel A. · Reviewed over 1 year ago

some issue with the labels, but after some witchery with the yaml being able to work it out

Igor T. · Reviewed over 1 year ago

Akansha W. · Reviewed over 1 year ago

Gloria K. · Reviewed over 1 year ago

sebastien D. · Reviewed over 1 year ago

Anthony L. · Reviewed over 1 year ago

Mariana L. · Reviewed over 1 year ago

Abhishek B. · Reviewed over 1 year ago

Deepak L. · Reviewed over 1 year ago

Sofia E. · Reviewed over 1 year ago

Paing Htoo N. · Reviewed over 1 year ago

Buena experiencia.

Rafael M. · Reviewed over 1 year ago

Robert G. · Reviewed over 1 year ago

Oscar J. · Reviewed over 1 year ago

Marek S. · Reviewed over 1 year ago

Kylie H. · Reviewed over 1 year ago

Michael M. · Reviewed over 1 year ago

Good examples of giving GKE permissions through service accounts and IAM Permissions, enjoyed the IP Address rotation of the GKE Cluster as an addition, would have been nice to have been marked on that one!

Justin E. · Reviewed over 1 year ago

KAI W. · Reviewed over 1 year ago

Michael Angelo Z. · Reviewed over 1 year ago

student_00_e614b07bad74@cloudshell:~ (qwiklabs-gcp-03-8d7e8f2024b6)$ gcloud container clusters update $my_cluster --zone $my_zone --complete-credential-rotation This will complete the in-progress Credential Rotation on cluster [standard-cluster-1]. The master will be updated to stop serving on the old IP address and only serve on the new IP address. Old cluster credentials will be invalidated. Make sure all API clients have been updated to communicate with the new IP address (e.g. by running `gcloud container clusters get-credentials --project qwiklabs-gcp-03-8d7e8f2024b6 --location us-central1-a standard-cluster-1`). If maintenence window is used, nodes are not recreated until a maintenance window occurs. See documentation https://cloud.google.com/kubernetes-engine/docs/how-to/credential-rotation on how to manually update nodes. This operation is long-running and will block other operations on the cluster (including delete) until it has run to completion. Do you want to continue (Y/n)? y ERROR: (gcloud.container.clusters.update) ResponseError: code=400, message=Node pool "default-pool" requires recreation. student_00_e614b07bad74@cloudshell:~ (qwiklabs-gcp-03-8d7e8f2024b6)$ gcloud container clusters upgrade $my_cluster --node-pool=default-pool --zone $my_zone All nodes in node pool [default-pool] of cluster [standard-cluster-1] will be upgraded from version [1.27.3-gke.100] to version [1.27.3-gke.100]. This operation is long-running and will block other operations on the cluster (including delete) until it has run to completion. Do you want to continue (Y/n)? y ERROR: (gcloud.container.clusters.upgrade) ResponseError: code=400, message=Cluster is running incompatible operation operation-1704226508383-92397857-74fe-4a23-bbcd-b2a907b83659. student_00_e614b07bad74@cloudshell:~ (qwiklabs-gcp-03-8d7e8f2024b6)$ ================ PS: problem does not occur when using K8S v1.28

Michel M. · Reviewed over 1 year ago

Jennifer L. · Reviewed over 1 year ago