Some of our containers run better with memory above the instance type currently deployed in our Container Engine cluster. Is there a recommended practice to rebuild the con
A different approach would be:
(1) to create a new node-pool to the GKE cluster with vertically scaled machine types ...
$ gcloud container node-pools create pool-n1std2 --zone europe-west1-d --cluster prod-cluster-1 --machine-type n1-standard-2 --image-type gci --disk-size=250 --num-nodes 3
(2) then, migrate the workloads off the old nodes ...
$ kubectl drain gke-prod-cluster-1-default-pool-f1eabad5-9ml5 --delete-local-data --force
(3) and finally, to delete the old node-pool
$ gcloud container node-pools delete default-pool --cluster=prod-cluster-1
Notes:
emptyDir !!!nodeSelector to schedule the pods onto the new pool. Label to be matched against would be cloud.google.com/gke-nodepool: pool-n1std2