blocks|key|2309210|text|Kubernetes本身没有当有新镜像时自动重新部署pods的功能。理想情况下，您需要的是一个支持GitOps样式部署的工具，其中git中的状态更改将同步到Kubernetes集群。有支持GitOps的Flux和ArgoCD开源工具。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2309211|最近出现了一个将这两个项目组合为ArgoFlux的announcement。|2309212|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/fluxcd/flux|1|https://argoproj.github.io/argo-cd/operator-manual/architecture/|2|https://www.weave.works/blog/argo-flux-join-forces^0|2T|4|0|2Y|6|1|0|P|C|2|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]|$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|F|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]|P|$5|I|J|K|C|$L|Q]]]]

Kubernetes natively does not have the feature of automatically redeploying pods when there is a new image. Ideally what you want is a tool which enables GitOps style deployment wherein state change in git will be synced to the Kubernetes cluster. There is <a href="https://github.com/fluxcd/flux" rel="noreferrer">Flux</a> and <a href="https://argoproj.github.io/argo-cd/operator-manual/architecture/" rel="noreferrer">ArgoCD</a> open source tools which supports GitOps. 

Recently there is an <a href="https://www.weave.works/blog/argo-flux-join-forces" rel="noreferrer">announcement</a> to combine these two projects as ArgoFlux.

blocks|key|394129|text|看一下各种image+pull+policies。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|394130|imagePullPolicy:+always可能最接近您的需求。我不知道在“香草”K8s中是否有一种方法可以实现自动图像拉取，但我知道RedHat的OpenShift+(或OKD，免费版本)可以与image+streams一起工作，它完全可以做你想要的事情。|style|CODE|394131|entityMap|0|LINK|mutability|MUTABLE|url|https://kubernetes.io/docs/concepts/configuration/overview/#container-images|1|https://blog.openshift.com/image-streams-faq/^0|5|J|0|0|0|N|2R|D|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@$A|W|B|X|F|G]]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|H|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

Have a look at the various <a href="https://kubernetes.io/docs/concepts/configuration/overview/#container-images" rel="nofollow noreferrer">image pull policies</a>. 

<code>imagePullPolicy: always</code> might come closest to what you need. I don't know if there is a way in "vanilla" K8s to achieve an automatic image pull, but I know that RedHat's OpenShift (or OKD, the free version) works with <a href="https://blog.openshift.com/image-streams-faq/" rel="nofollow noreferrer">image streams</a>, which do exactly what you ask for.

blocks|key|2304270|text|当kubelet尝试拉取指定的图像时，会影响图像的imagePullPolicy和标签。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2304271|imagePullPolicy:+IfNotPresent：仅当本地尚未存在镜像时，才会拉取该镜像。|offset|length|style|CODE|2304272|imagePullPolicy:+Always**：实例每次启动都会拉取镜像。**|BOLD|2304273|省略imagePullPolicy，图像标记为:latest或省略:始终应用。|2304274|省略了imagePullPolicy，并且存在图像标记，但应用了:latest:+IfNotPresent。|2304275|imagePullPolicy:+Never：假设镜像存在于本地。不会尝试拉取图像。|2304276|因此，为了实现这一点，你必须设置imagePullPolicy:+Always+并重新启动你的pod，它应该会拉出一个最新的镜像副本。我不认为在K8s中有任何其他方法|2304277|Container+Images|2304278|entityMap|0|LINK|mutability|MUTABLE|url|https://kubernetes.io/docs/concepts/configuration/overview/#container-images^0|0|0|T|0|0|P|0|N|0|2|F|0|3|F|0|0|M|0|G|N|G|N|0|0|G|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@$D|14|E|15|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|16|8|@$D|17|E|18|F|J]|$D|19|E|1A|F|G]]|9|@]|A|$]]|$1|K|3|L|5|6|7|1B|8|@$D|1C|E|1D|F|G]]|9|@]|A|$]]|$1|M|3|N|5|6|7|1E|8|@$D|1F|E|1G|F|G]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1H|8|@$D|1I|E|1J|F|G]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1K|8|@$D|1L|E|1M|F|J]|$D|1N|E|1O|F|G]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1P|8|@]|9|@$D|1Q|E|1R|1|1S]]|A|$]]|$1|U|3|-4|5|6|7|1T|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]]]

The imagePullPolicy and the tag of the image affect when the kubelet attempts to pull the specified image.

<code>imagePullPolicy: IfNotPresent</code>: the image is pulled only if it is not already present locally.

<code>imagePullPolicy: Always</code>: the image is pulled every time the pod is started.

<code>imagePullPolicy</code> is omitted and either the image tag is :latest or it is omitted: Always is applied.

<code>imagePullPolicy</code> is omitted and the image tag is present but not :latest: IfNotPresent is applied.

<code>imagePullPolicy: Never</code>: the image is assumed to exist locally. No attempt is made to pull the image.

So to achieve this you have to set <code>imagePullPolicy: Always</code> and restart you pod and it should pull a fresh latest copy of image. I don't think there is any other way in K8s

<a href="https://kubernetes.io/docs/concepts/configuration/overview/#container-images" rel="nofollow noreferrer">Container Images</a>

blocks|key|5490030|text|您应该为每个构建分配某种类型的唯一标识符。这可以基于源代码控制标记(如果显式标记发布)、提交ID、版本号、时间戳或其他东西；但重要的细节是，每个构建都会创建一个具有唯一名称的唯一映像。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5490031|一旦这样做了，您的CI系统就需要使用新的image:更新部署规范。如果您使用Kustomize或Helm这样的工具，有一些标准模式可以提供此功能；如果您直接使用kubectl+apply，则在应用它之前，它需要以某种方式修改部署规范。|offset|length|style|CODE|5490032|这种组合意味着部署的嵌入式pod规范将以某种实质性的方式发生变化(其image:发生了变化)，这将导致Kubernetes部署控制器自动为您进行滚动更新。如果出现问题，普通的Kubernetes回滚机制将正常工作(因为带有昨天标记的图像仍在您的存储库中)。您不需要手动设置imagePullPolicy:或手动导致部署重启，在部署中更改映像标签就足以导致正常部署。|5490033|entityMap^0|0|K|6|28|D|0|Y|6|3S|G|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]|$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@$D|S|E|T|F|G]|$D|U|E|V|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|K|$]]

You should assign some sort of unique identifier to each build. This could be based off a source-control tag (if you explicitly tag releases), a commit ID, a build number, a time stamp, or something else; but the important detail is that each build creates a unique image with a unique name.

Once you do that, then your CI system needs to update the Deployment spec with a new <code>image:</code>. If you're using a tool like Kustomize or Helm, there are standard patterns to provide this; if you are using <code>kubectl apply</code> directly, it will need to modify the deployment spec in some way before it applies it.

This combination of things means that the Deployment's embedded pod spec will have changed in some substantial way (its <code>image:</code> has changed), which will cause the Kubernetes deployment controller to automatically do a rolling update for you. If this goes wrong, the ordinary Kubernetes rollback mechanisms will work fine (because the image with yesterday's tag is still in your repository). You do not need to manually set <code>imagePullPolicy:</code> or manually cause the deployment to restart, changing the image tag in the deployment is enough to cause a normal rollout to happen.

blocks|key|3378563|text|我刚刚写了一个bash脚本来实现this.My+imagePullPolicy选项是始终的，我正在用crontab运行这个脚本。(你可以用无限循环检查每一次).It正在检查存储库，如果发生任何变化，它会删除pod+(由于imagePullPolicy设置为always而自动)并拉取更新的映像。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3378564|#!/bin/bash
registry="repository_name"
username="user_name"
password="password"

##BY+this+you+can+append+all+images+from+repository+to+the+array
#images=($(+echo+$(curl+-s+https://"$username":"$password"@"$registry"/v2/_catalog+%7C+jq+.repositories+%7C+jq+.[])))
##Or+you+can+set+manuaaly+your+image+array
images=(+image_name_0+image_name_1+)
for+i+in+"${images[@]}"
do
old_image=$(cat+/imagerecords/"$i".txt)
new_image=$(echo+$(curl+-s+https://"$username":"$password"@"$registry"/v2/"$i"/manifests/latest+%7C+jq+."fsLayers"+%7C+jq+.[]))


if+[+"$old_image"+==+"$new_image"+];then
echo+"image:+"$i"+is+already+up-to-date"
else
echo+"image:+"+$i"+is+updating"
kubectl+delete+pod+pod_name
echo+$new_image+>+/imagerecords/"$i".txt
fi
done|code-block|syntax|javascript|3378565|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I just wrote a bash script to achieve this.My imagePullPolicy option is always and i am running this script with crontab.(You can check everytime with infinite loops).It is checking repository and if any change occured , it is deleting the pod (automatically because of imagePullPolicy set Always) and pulling updated image.

<pre><code>#!/bin/bash
registry="repository_name"
username="user_name"
password="password"

##BY this you can append all images from repository to the array
#images=($( echo $(curl -s https://"$username":"$password"@"$registry"/v2/_catalog | jq .repositories | jq .[])))
##Or you can set manuaaly your image array
images=( image_name_0 image_name_1 )
for i in "${images[@]}"
do
old_image=$(cat /imagerecords/"$i".txt)
new_image=$(echo $(curl -s https://"$username":"$password"@"$registry"/v2/"$i"/manifests/latest | jq ."fsLayers" | jq .[]))


if [ "$old_image" == "$new_image" ];then
echo "image: "$i" is already up-to-date"
else
echo "image: " $i" is updating"
kubectl delete pod pod_name
echo $new_image &gt; /imagerecords/"$i".txt
fi
done
</code></pre>

blocks|key|3378603|text|此功能由开源项目argocd-image-updater提供|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3378604|https://github.com/argoproj-labs/argocd-image-updater|3378605|entityMap|0|LINK|mutability|MUTABLE|url^0|8|K|0|0|1H|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|R|8|@]|D|@$9|S|A|T|1|U]]|E|$]]|$1|H|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|G]]]]

This functionality is provided by open-source project <code>argocd-image-updater</code>:
<a href="https://github.com/argoproj-labs/argocd-image-updater" rel="nofollow noreferrer">https://github.com/argoproj-labs/argocd-image-updater</a>

I have a private repository. I want to update my image on Kubernetes automatically when the image is updated on this private repository. How can I achieve this?

Auto Update Container Image When New Build Released on Kubernetes

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个私有的仓库。我希望在这个私有存储库上更新镜像时，自动更新Kubernetes上的镜像。我如何才能做到这一点？

问在Kubernetes上发布新版本时自动更新容器镜像
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Kubernetes上发布新版本时自动更新容器镜像EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Kubernetes上发布新版本时自动更新容器镜像
EN