Upgrading node pools in GKE

[@googlecloudtech]

🔗 What node pool upgrade strategy works best for you? Let us know in the comments and be sure to subscribe for future GKE videos! → goo.gle/GoogleCloudTech

[@gauravpande7746]

Hi , thanks for this video. In Blue Green Upgrade does GKE creates a duplicate node Pool itself or it updates the existing node Pool to have upgraded version of kubernetes?

[@anthonybushong]

@@gauravpande7746 Hi Gaurav! Great question. In the same Node Pool, it creates a new set of Nodes with the new version side by side with the old set of Nodes. You then can configure how and when to turn down the old set of Nodes.

[@gauravpande7746]

@@anthonybushong Ahhh.. are you sure ? doc says I think it creates new node Pool with the same config as old node Pool but with new node Pool has nodes having new kubernetes version

[@anthonybushong]

@@gauravpande7746 new _managed instance groups_ are created. a node pool can be made up of multiple managed instance groups, which is an underlying GCE VM construct. this is helpful feedback, i should have included that concept in the video!

[@kanishkahalder7642]

There seems to be a mismatch in the video and what Anthony is saying @googlecloudtech at 5:26 #------ max-surge-upgrade=20 max-unavailable-upgrade=0 ------- this should ensure more resources for pods and limit disruption but increase cost #------ max-surge-upgrade=0 max-unavailable-upgrade=20 ------- this would allow nodes to be destroyed faster than they are created am I missing something here ?

[@anthonybushong4670]

Hi Kanish - good catch! We had the configuration in the visual in the wrong order - that's our mistake. Thank you for outlining it for future viewers.

[@ravichanderkt326]

Thanks Anthony ❤

[@albab790]

Thank you