Securing Google Kubernetes Engine with IAM and Pod Security Admission Reviews

Some commands or permissions got changed and incorrect in the description. Please check and fix it

Tanya D. · Reviewed about 1 year ago

Alex H. · Reviewed about 1 year ago

Janani P. · Reviewed about 1 year ago

Ria P. · Reviewed about 1 year ago

Shiva Raj K. · Reviewed about 1 year ago

Michal W. · Reviewed about 1 year ago

Radhika A. · Reviewed about 1 year ago

RYAN S. · Reviewed about 1 year ago

Andres A. · Reviewed about 1 year ago

does not work

xianzhan l. · Reviewed about 1 year ago

Jacob M. · Reviewed about 1 year ago

Kamran S. · Reviewed about 1 year ago

Miguel Angel S. · Reviewed about 1 year ago

Devendra S. · Reviewed about 1 year ago

ANJALI S. · Reviewed about 1 year ago

vinopal J. · Reviewed about 1 year ago

Przemyslaw O. · Reviewed about 1 year ago

Rengaraju B. · Reviewed about 1 year ago

German A. · Reviewed about 1 year ago

pp

Lakshmi P. · Reviewed about 1 year ago

Kanishka S. · Reviewed about 1 year ago

KEVIN D. · Reviewed about 1 year ago

Jeannine H. · Reviewed about 1 year ago

Rotating IP address and creds failed and the update to fix it failed as well: student_04_48e4ff4abbf0@cloudshell:~ (qwiklabs-gcp-00-dd74c0d3810c)$ 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-00-dd74c0d3810c --location us-east4-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_04_48e4ff4abbf0@cloudshell:~ (qwiklabs-gcp-00-dd74c0d3810c)$

Dwayne G. · Reviewed about 1 year ago

Paula C. · Reviewed about 1 year ago