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 около 1 года ago

Alex H. · Reviewed около 1 года ago

Janani P. · Reviewed около 1 года ago

Ria P. · Reviewed около 1 года ago

Shiva Raj K. · Reviewed около 1 года ago

Michal W. · Reviewed около 1 года ago

Radhika A. · Reviewed около 1 года ago

RYAN S. · Reviewed около 1 года ago

Andres A. · Reviewed около 1 года ago

does not work

xianzhan l. · Reviewed около 1 года ago

Jacob M. · Reviewed около 1 года ago

Kamran S. · Reviewed около 1 года ago

Miguel Angel S. · Reviewed около 1 года ago

Devendra S. · Reviewed около 1 года ago

ANJALI S. · Reviewed около 1 года ago

vinopal J. · Reviewed около 1 года ago

Przemyslaw O. · Reviewed около 1 года ago

Rengaraju B. · Reviewed около 1 года ago

German A. · Reviewed около 1 года ago

pp

Lakshmi P. · Reviewed около 1 года ago

Kanishka S. · Reviewed около 1 года ago

KEVIN D. · Reviewed около 1 года ago

Jeannine H. · Reviewed около 1 года 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 около 1 года ago

Paula C. · Reviewed около 1 года ago