kubernetes/ingress-nginx

Zero downtime upgrade

Open

#6,928 创建于 2021年3月4日

在 GitHub 查看
 (36 评论) (9 反应) (0 负责人)Go (15,199 star) (7,888 fork)batch import
help wantedkind/supportneeds-triagepriority/important-soon

描述

Docs (https://github.com/kubernetes/ingress-nginx/tree/master/charts/ingress-nginx#upgrading-with-zero-downtime-in-production) are mentioning that by default during an upgrade there is a service interruption caused by pods being restarted, and another article is linked with explanation how one can fix that.

But when looking at values.yml I can see both terminationGracePerios and preStop hook is set correctly in order to drain connections.

https://github.com/kubernetes/ingress-nginx/blob/a7fb791132a0dee285b47d0041f4f9acf1e7cff8/charts/ingress-nginx/values.yaml#L237

https://github.com/kubernetes/ingress-nginx/blob/a7fb791132a0dee285b47d0041f4f9acf1e7cff8/charts/ingress-nginx/values.yaml#L583-L587

Is the documentation a little bit outdated or there is something else that I should set to get near zero downtime upgrades?

贡献者指南

技术栈
gokubernetesdocker
领域
devopsinfrastructurecloud
议题类型
documentation
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
basic kubernetes knowledgehelm chart configurationunderstanding of pod lifecycle hooks
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
30
研究方向
Investigate the helm chart values for terminationGracePeriodSeconds and preStop hook in ingress nginx (see values.yaml lines 237, 583-587). Compare with the linked documentation on zero downtime upgrades. Determine if the documentation is outdated or if additional configuration is needed. Check the referenced article for zero downtime strategies and test the behavior during a rolling update. Consider updating the documentation or values if inconsistencies are found.