Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

post/configmap-rollout-followup/ #7

Open
utterances-bot opened this issue May 22, 2019 · 5 comments
Open

post/configmap-rollout-followup/ #7

utterances-bot opened this issue May 22, 2019 · 5 comments

Comments

@utterances-bot
Copy link

Kubernetes 中的 ConfigMap 配置更新(续)

https://aleiwu.com/post/configmap-rollout-followup/

Copy link

大神 你之前的数据同步项目 有没有相关blog

@aylei
Copy link
Owner

aylei commented May 22, 2019

@fuxiangduan
是指 https://aleiwu.com/post/vimur.cn/ 吗? 很早写的了

Copy link

对对,多谢了,参考参考

Copy link

Copy link

whzzx commented Dec 2, 2019

文章最后提到:通过Helm可实现ConfigMap Rollout,但我在实际测试过程中,更改configmap.data后,helm会马上新建new configmap,并删除old configmap;如果new configmap有问题,pod滚动更新会卡住,但假如其它尚未重建的pod挂掉重启,会出现old configmap not found。
请问如何设置,可以保证old configmap只有在不被任何pod引用的情况下,才被helm删除?
谢谢!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants