大网数据广告活动
服务器运维问答

Kubernetes: detect and auto-update deployment on image update

· 52CE 我爱测

We're running multiple, globally distributed Kubernetes clusters that need to run the same software. When we release an update to this software (as a Docker image uploaded to a private Docker repo), our current deployment pipelin…

问题原文

原帖链接 · shevron · CC BY-SA 4.0

We're running multiple, globally distributed Kubernetes clusters that need to run the same software. When we release an update to this software (as a Docker image uploaded to a private Docker repo), our current deployment pipeline needs to iterate over a list of known deployments, connect to each cluster and update the right Deployment there. This is a cumbersome, fragile, slow and non-scalable process.

I'm looking for a way to solve this by creating deployments that periodically check for a new Docker image version and when they detect a change, they pull the new image and update the right Deployment. This should be done by each cluster independently so there's no central process connecting to each cluster and a list of clusters to maintain etc.

There is no requirement that all clusters update at the same time, but the idea is to have eventual consistency with no central management.

Is there an existing tool that does this or solves this problem in a different way?

已采纳解答

原帖链接 · Leonid Mirsky · CC BY-SA 4.0

Sounds like Weave's Flux answers your requirements:

https://github.com/weaveworks/flux

We have it installed in one of our customer's cluster and it works great. It will watch for changes to your Docker images and perform a redeploment. Kinda exactly how you described it in your question.

The project is a bit new so setting it up can be a bit tedious... But eventually it works!

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2018-09-20)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。