Upgrading your Cluster with Zero Downtime

Upgrading your Cluster with Zero Downtime

Google Cloud Tech

6 лет назад

41,184 Просмотров

Ссылки и html тэги не поддерживаются


Комментарии:

Anil Kumar
Anil Kumar - 11.10.2022 09:31

If we were to update Node-selector in every Name-space deployment yaml file, we could not proceed in this manner. The new node pool name must be updated in the NodeSelector yaml file section, and then the instructions must be followed.

Provide the solution when node-selector is enabled in every yaml file. How to efficiently complete the task of upgrading.

Ответить
Vishwanath K
Vishwanath K - 13.11.2020 22:11

When you cordon and drain the node one at a time, there is a chance that the drained pods can get scheduled on old node pool nodes and not necessarily on new node pool nodes.

Ответить
Cyber Stair
Cyber Stair - 14.07.2020 23:07

Please upload more videos on this topics

Ответить
Adam Furtenbach
Adam Furtenbach - 23.08.2019 14:51

Cordon not only makes a node nonscheduled for new pods, but also the Load balancer no longer redirect traffic to perfectly healthy pods on a cordoned node.

Ответить
Jardel Weyrich
Jardel Weyrich - 11.04.2019 01:51

Great lesson! Thank you for this!

Ответить
Stoune
Stoune - 14.12.2018 22:15

Should this recommendation be deprecated in favor of using deployments and Horizontal Pod Autoscaler?

Ответить
Bhavikatti Praveen
Bhavikatti Praveen - 10.10.2018 20:20

nice explanation sandeep
and i would like to know any official online course in advance level ,already i have some idea till intermediate level practiced too from offical docs and i wanna do more complex projects or tasks under your training ?????? .... urgently from your end Sandeep

Ответить
IceW4ve
IceW4ve - 02.06.2018 12:03

Very good explanation, as always. Thanks!

Ответить