Securing Google Kubernetes Engine with IAM and Pod Security Admission Reviews
Loading...
No results found.

Apply your skills in Google Cloud console

Securing Google Kubernetes Engine with IAM and Pod Security Admission Reviews

4621 reviews

Binay M. · Reviewed מעל שנה אחת ago

tom y. · Reviewed מעל שנה אחת ago

jack B. · Reviewed מעל שנה אחת ago

Gabriel A. · Reviewed מעל שנה אחת ago

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

Igor T. · Reviewed מעל שנה אחת ago

Akansha W. · Reviewed מעל שנה אחת ago

Gloria K. · Reviewed מעל שנה אחת ago

sebastien D. · Reviewed מעל שנה אחת ago

Anthony L. · Reviewed מעל שנה אחת ago

Mariana L. · Reviewed מעל שנה אחת ago

Abhishek B. · Reviewed מעל שנה אחת ago

Deepak L. · Reviewed מעל שנה אחת ago

Sofia E. · Reviewed מעל שנה אחת ago

Paing Htoo N. · Reviewed מעל שנה אחת ago

Buena experiencia.

Rafael M. · Reviewed מעל שנה אחת ago

Robert G. · Reviewed מעל שנה אחת ago

Oscar J. · Reviewed מעל שנה אחת ago

Marek S. · Reviewed מעל שנה אחת ago

Kylie H. · Reviewed מעל שנה אחת ago

Michael M. · Reviewed מעל שנה אחת 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 מעל שנה אחת ago

KAI W. · Reviewed מעל שנה אחת ago

Michael Angelo Z. · Reviewed מעל שנה אחת 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 מעל שנה אחת ago

Jennifer L. · Reviewed מעל שנה אחת ago

We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.