在Kubernetes中更新configmap时重启Pod吗? [英] Restart pods when configmap updates in Kubernetes?

问题描述

更改/更新它们的configmap后，如何自动重新启动Kubernetes Pod和与部署关联的Pod?

How do I automatically restart Kubernetes pods and pods associated with deployments when their configmap is changed/updated?

我知道有人谈论过在配置映射更改时自动重启Pod的功能，但据我所知，Kubernetes 1.2尚不提供此功能.

I know there's been talk about the ability to automatically restart pods when a config maps changes but to my knowledge this is not yet available in Kubernetes 1.2.

所以(我认为)我想做的是 deployment 资源.是否可以(如果可以的话)如何强制在Kubernetes中滚动重启部署，而无需更改实际模板中的任何内容?这是目前最好的方法还是有更好的选择?

So what (I think) I'd like to do is a "rolling restart" of the deployment resource associated with the pods consuming the config map. Is it possible, and if so how, to force a rolling restart of a deployment in Kubernetes without changing anything in the actual template? Is this currently the best way to do it or is there a better option?

推荐答案

在配置映射更新上对Pod进行签名是工作中的一项功能(

Signalling a pod on config map update is a feature in the works (https://github.com/kubernetes/kubernetes/issues/22368).

您始终可以编写一个自定义pid1来通知confimap已更改，然后重新启动您的应用程序.

You can always write a custom pid1 that notices the confimap has changed and restarts your app.

您还可以例如:在2个容器中装载相同的配置图，在第二个容器中公开http运行状况检查，如果配置图内容的哈希值发生更改，则该检查将失败，并将其作为第一个容器的活跃度探针(因为Pod中的容器共享相同的网络名称空间).当探测失败时，kubelet将为您重新启动第一个容器.

You can also eg: mount the same config map in 2 containers, expose a http health check in the second container that fails if the hash of config map contents changes, and shove that as the liveness probe of the first container (because containers in a pod share the same network namespace). The kubelet will restart your first container for you when the probe fails.

当然，如果您不关心Pod位于哪个节点，则只需删除它们，复制控制器就会为您重新启动"它们.

Of course if you don't care about which nodes the pods are on, you can simply delete them and the replication controller will "restart" them for you.

这篇关于在Kubernetes中更新configmap时重启Pod吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！