Como proteger o Google Kubernetes Engine com o IAM e a admissão de segurança do pod avaliações

tom y. · Revisado há over 1 year

jack B. · Revisado há over 1 year

Gabriel A. · Revisado há over 1 year

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

Igor T. · Revisado há over 1 year

Akansha W. · Revisado há over 1 year

Gloria K. · Revisado há over 1 year

sebastien D. · Revisado há over 1 year

Anthony L. · Revisado há over 1 year

Mariana L. · Revisado há over 1 year

Abhishek B. · Revisado há over 1 year

Deepak L. · Revisado há over 1 year

Sofia E. · Revisado há over 1 year

Paing Htoo N. · Revisado há over 1 year

Buena experiencia.

Rafael M. · Revisado há over 1 year

Robert G. · Revisado há over 1 year

Oscar J. · Revisado há over 1 year

Marek S. · Revisado há over 1 year

Kylie H. · Revisado há over 1 year

Michael M. · Revisado há over 1 year

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. · Revisado há over 1 year

KAI W. · Revisado há over 1 year

Michael Angelo Z. · Revisado há over 1 year

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. · Revisado há over 1 year

Jennifer L. · Revisado há over 1 year

second time was fine - all OK

DevAnd O. · Revisado há over 1 year