blocks|key|2240207|text|在kubectl+1.6中，-o+wide选项可以做到这一点，所以|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2240208|kubectl+get+deployments+-o+wide|code-block|syntax|javascript|2240209|将在输出中显示当前图像。|2240210|entityMap^0|1|7|E|7|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

From <code>kubectl</code> 1.6 the <code>-o wide</code> option does this, so

<pre><code>kubectl get deployments -o wide
</code></pre>

will show the current image in the output.

blocks|key|1590090|text|您可以使用kubectl的jsonpath输出选项来实现以下目标：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1590091|kubectl+get+deployment+flags+-o=jsonpath='{$.spec.template.spec.containers[:1].image}'|code-block|syntax|javascript|1590092|entityMap|0|LINK|mutability|MUTABLE|url|http://goessner.net/articles/JsonPath/^0|D|8|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

You can use kubectl's <a href="http://goessner.net/articles/JsonPath/" rel="noreferrer">jsonpath</a> output option to achieve this:

<pre><code>kubectl get deployment flags -o=jsonpath='{$.spec.template.spec.containers[:1].image}'
</code></pre>

blocks|key|1590184|text|要获得所有豆荚的图像uri+(例如，在所有名称空间中)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1590185|kubectl+get+pods+--all-namespaces+-o+jsonpath="{..image}"|offset|length|style|CODE|1590186|(更多细节请参见https://kubernetes.io/docs/tasks/access-application-cluster/list-all-running-container-images/+)|1590187|entityMap|0|LINK|mutability|MUTABLE|url|https://kubernetes.io/docs/tasks/access-application-cluster/list-all-running-container-images/^0|0|0|1L|0|8|2M|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

to get just the image uri for all pods (in all namespaces, for example):

<code>kubectl get pods --all-namespaces -o jsonpath="{..image}"</code>

(see <a href="https://kubernetes.io/docs/tasks/access-application-cluster/list-all-running-container-images/" rel="noreferrer">https://kubernetes.io/docs/tasks/access-application-cluster/list-all-running-container-images/</a> for more detail)

blocks|key|2989995|text|对于单个部署，请使用以下命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2989996|kubectl+get+deploy/deployment-name+-o+jsonpath="{..image}"|code-block|syntax|javascript|2989997|它也适用于豆荚|2989998|kubectl+get+pod/pod-name+-o+jsonpath="{..image}"|2989999|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

For a single deployment use this:

<pre><code>kubectl get deploy/deployment-name -o jsonpath="{..image}"
</code></pre>

It can work for pod too

<pre><code>kubectl get pod/pod-name -o jsonpath="{..image}"
</code></pre>

blocks|key|2240258|text|您可以在一个列表中列出所有部署的映像标记：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2240259|kubectl+get+deployment+-o=jsonpath="{range+.items[*]}{'\n'}{.metadata.name}{':\t'}{range+.spec.template.spec.containers[*]}{.image}{',+'}{end}{
end}"|code-block|syntax|javascript|2240260|样本输出：|2240261|deployment-a:+++docker-registry.com/group/image-a:v1,
deployment-b:+++docker-registry.com/group/image-b:v2,
deployment-c:+++docker-registry.com/group/image-c:v3,
deployment-d:+++docker-registry.com/group/image-d:v4,|2240262|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

You can list all deployments' image tag in a list:

<pre><code>kubectl get deployment -o=jsonpath="{range .items[*]}{'\n'}{.metadata.name}{':\t'}{range .spec.template.spec.containers[*]}{.image}{', '}{end}{
end}"
</code></pre>

Sample output:

<pre><code>deployment-a: docker-registry.com/group/image-a:v1,
deployment-b: docker-registry.com/group/image-b:v2,
deployment-c: docker-registry.com/group/image-c:v3,
deployment-d: docker-registry.com/group/image-d:v4,
</code></pre>

blocks|key|2989900|text|以下几点对我有用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2989901|kubectl+get+deployment+-o=jsonpath='{$.items[:1].spec.template.spec.containers[:1].image}'|code-block|syntax|javascript|2989902|由于某种原因，..my部署配置显然是不同的(开头是“items”元素)。|2989903|UPDATE:如果只执行以下操作，就会出现'items‘元素(它只是部署元素的列表)：|2989904|kubectl+get+deployment+-o=json|2989905|然而，如果我指定部署名称，则返回的json中将没有items元素，例如：|2989906|kubectl+get+deployment+[deploymentName]+-o=json|2989907|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|W|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|Y|8|@]|9|@]|A|$E|F]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

the following worked for me:

<pre><code>kubectl get deployment -o=jsonpath='{$.items[:1].spec.template.spec.containers[:1].image}'
</code></pre>

..my deployment config was clearly different (with 'items' element at the start) for some reason.

UPDATE:
The 'items' element (which is just a list of deployment elements) will appear if just doing:

<pre><code>kubectl get deployment -o=json
</code></pre>

whereas if I specify the deployment name, there'll be no items element in the returned json, e.g.:

<pre><code>kubectl get deployment [deploymentName] -o=json
</code></pre>

blocks|key|2240298|text|你可以用，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2240299|kubectl++get+pod+<pod_name>++-o+yaml%7C+grep+image:|offset|length|style|CODE|2240300|从部署上看，|2240301|kubectl++get+deploy+<deployment_name>++-o+yaml%7C+grep+image:|2240302|entityMap^0|0|0|1D|0|0|0|1N|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|M|$]]

You can use,

<code>kubectl get pod &lt;pod_name&gt; -o yaml| grep image:</code>

And from deployment,

<code>kubectl get deploy &lt;deployment_name&gt; -o yaml| grep image:</code>

blocks|key|2240409|text|其他答案中提到的方法，如|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2240410|kubectl+get+deployment+deploymentname+-o=jsonpath='{$.spec.template.spec.containers[:1].image}'|code-block|syntax|javascript|2240411|返回图像，即使当前的推出不成功。如果您想从成功的/运行的荚中获取图像，请使用此方法。|2240412|kubectl+get+po+-l+app=deploymentname+--field-selector+status.phase=Running++-o=jsonpath='{.items[*].spec.containers[*].image}'|2240413|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Approaches mentioned in other answers like
<pre><code>kubectl get deployment deploymentname -o=jsonpath='{$.spec.template.spec.containers[:1].image}'
</code></pre>
return image even if current rollout is unsuccessful. Use this approach if you want to get image from successful/running pod
<pre><code>kubectl get po -l app=deploymentname --field-selector status.phase=Running -o=jsonpath='{.items[*].spec.containers[*].image}'
</code></pre>

blocks|key|1590301|text|要获取部署所使用的所有映像，可以使用下面的命令。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1590302|kubectl+get+pods+--all-namespaces+-o=jsonpath='{range+.items[*]}{"\n"}{.metadata.name}{":\t"}{range+.spec.containers[*]}{.image}{",+"}{end}{end}'+%7C\+sort|code-block|syntax|javascript|1590303|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|$]]

To get all the images being used by the deployments, you can use below command.
<pre><code>kubectl get pods --all-namespaces -o=jsonpath='{range .items[*]}{&quot;\n&quot;}{.metadata.name}{&quot;:\t&quot;}{range .spec.containers[*]}{.image}{&quot;, &quot;}{end}{end}' |\ sort
</code></pre>

blocks|key|2240324|text|kubectl+get+deployments.apps+-n+admin2406+-o=custom-columns=DEPLOYMENT:.metadata.name,CONTAINER_IMAGE:.spec.template.spec.containers[*].image,READY_REPLICAS:.status.readyReplicas,NAMESPACE:.metadata.namespace|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|2240325|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>kubectl get deployments.apps -n admin2406 -o=custom-columns=DEPLOYMENT:.metadata.name,CONTAINER_IMAGE:.spec.template.spec.containers[*].image,READY_REPLICAS:.status.readyReplicas,NAMESPACE:.metadata.namespace
</code></pre>

blocks|key|2240465|text|如果您正在寻找部署，它将是特定于部署的，但是如果您想在所有对象中搜索映像，例如:部署、状态集、去角色、作业等，那么下面的简单命令就可以了：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2240466|kubectl+get+all+-n+<namespace>+-o+jsonpath={..image}}+%7C+tr+'+'+'\n'+%7C+sort+-u|code-block|syntax|javascript|2240467|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|$]]

If you are looking for deployment, it would be deployment specific, but if one wants to search images in all objects like: deployment, statefulset, demaonset, jobs etc, the following simple command would do the trick:
<pre><code>kubectl get all -n &lt;namespace&gt; -o jsonpath={..image}} | tr ' ' '\n' | sort -u
</code></pre>

blocks|key|2990114|text|即使这个问题已经得到了回答，我还是想提供一个使用Go模板的例子：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2990115|kubectl+get+deployment+$GKE_DEPLOYMENT_NAME+\
--namespace=$GKE_DEPLOYMENT_NAMESPACE+\
--output=go-template+\
--template='{{range+.spec.template.spec.containers}}{{.image}}{{"\n"}}{{end}}'

#=>

us.gcr.io/.+.+./.+.+.:xxxxxxx|code-block|syntax|javascript|2990116|备注：如果您的deployment包含多个容器，此命令将列出all+Docker映像；因为containers要么是JSON数组，要么是YAML序列，所以没有保证的顺序。也就是说，“按元素选择”索引不能保证返回预期的Docker。还有标签。|offset|length|style|BOLD|CODE|2990117|注意事项：如果您使用此命令来确定当前部署了什么git+commit，则需要通过Docker标记或Docker标签引入字符串操作。|2990118|您可能需要label您的deployment而不是|2990119|kubectl+label+\
--overwrite=true+\
deployment+$GKE_DEPLOYMENT_NAME+\
commit=$(git+rev-parse+--short+HEAD)+\
--namespace=$GKE_DEPLOYMENT_NAMESPACE+\
--record=true

#=>

deployment.apps/$GKE_DEPLOYMENT_NAME+labeled|2990120|并使用以下方法访问此label，而不考虑多个Docker映像和不需要字符串操作的：|2990121|kubectl+get+deployment+$GKE_DEPLOYMENT_NAME+\
--namespace=$GKE_DEPLOYMENT_NAMESPACE+\
--output=go-template+\
--template='{{index+.metadata.labels+"commit"}}{{"\n"}}'

#=>

xxxxxxx|2990122|entityMap^0|0|0|0|2|U|3|7|A|19|A|0|0|4|N|3|R|6|0|5|5|C|A|0|0|A|5|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|10|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|11|8|@$I|12|J|13|K|L]|$I|14|J|15|K|L]|$I|16|J|17|K|M]|$I|18|J|19|K|M]]|9|@]|A|$]]|$1|N|3|O|5|6|7|1A|8|@$I|1B|J|1C|K|L]|$I|1D|J|1E|K|M]|$I|1F|J|1G|K|M]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1H|8|@$I|1I|J|1J|K|M]|$I|1K|J|1L|K|M]]|9|@]|A|$]]|$1|R|3|S|5|D|7|1M|8|@]|9|@]|A|$E|F]]|$1|T|3|U|5|6|7|1N|8|@$I|1O|J|1P|K|M]]|9|@]|A|$]]|$1|V|3|W|5|D|7|1Q|8|@]|9|@]|A|$E|F]]|$1|X|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]]|Y|$]]

Even though the question has already been answered, I wanted to provide an example using Go templating:
<pre class="lang-sh prettyprint-override"><code>kubectl get deployment $GKE_DEPLOYMENT_NAME \
--namespace=$GKE_DEPLOYMENT_NAMESPACE \
--output=go-template \
--template='{{range .spec.template.spec.containers}}{{.image}}{{&quot;\n&quot;}}{{end}}'

#=&gt;

us.gcr.io/. . ./. . .:xxxxxxx
</code></pre>
Note: if your <code>deployment</code> contains more than one container, this command will list all Docker Images; since <code>containers</code> is either a JSON array or YAML sequence, there is no guaranteed order. I.e. selecting by element index isn't guaranteed to return the intended Docker Image Repo. and Tag.
Note: if you are using this command in order to determine what <code>git</code> <code>commit</code> is currently deployed, through Docker Tags or Docker Labels, you will need to introduce string manipulation.
You may want to <code>label</code> your <code>deployment</code> instead:
<pre class="lang-sh prettyprint-override"><code>kubectl label \
--overwrite=true \
deployment $GKE_DEPLOYMENT_NAME \
commit=$(git rev-parse --short HEAD) \
--namespace=$GKE_DEPLOYMENT_NAMESPACE \
--record=true

#=&gt;

deployment.apps/$GKE_DEPLOYMENT_NAME labeled
</code></pre>
and access this <code>label</code>, regardless of multiple Docker Images and without string manipulation, using:
<pre class="lang-sh prettyprint-override"><code>kubectl get deployment $GKE_DEPLOYMENT_NAME \
--namespace=$GKE_DEPLOYMENT_NAMESPACE \
--output=go-template \
--template='{{index .metadata.labels &quot;commit&quot;}}{{&quot;\n&quot;}}'

#=&gt;

xxxxxxx
</code></pre>

blocks|key|2240431|text|被接受的答案给出提示，但如果有人正在寻找问题中的工作示例|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2240432|kubectl+-n+dev+get+sts++-l+'app+in+(app1,app2)'+-o+wide+--no-headers+%7C+awk+'{print+$5}'+|code-block|syntax|javascript|2240433|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|$]]

Accepted answer give hint but if someone is looking for working example as asked in question
<pre><code>kubectl -n dev get sts -l 'app in (app1,app2)' -o wide --no-headers | awk '{print $5}' 
</code></pre>

blocks|key|2240471|text|可以使用自定义列获取图像名称。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2240472|kubectl+get+deploy+-o+custom-columns=DEPLOYMENT-NAME:.metadata.name,IMAGE-NAME:.spec.template.spec.containers[*].image|code-block|syntax|javascript|2240473|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|$]]

You can use custom column to get the image name
<pre><code>kubectl get deploy -o custom-columns=DEPLOYMENT-NAME:.metadata.name,IMAGE-NAME:.spec.template.spec.containers[*].image
</code></pre>

How can I use <code>kubectl</code> or the API to retrieve the current image for containers in a pod or deployment?

For example, in a deployment created with the below configuration, I want to retrieve the value <code>eu.gcr.io/test0/brain:latest</code>.

<pre><code>apiVersion: v1
 kind: Deployment
 metadata:
 name: flags
 spec:
 replicas: 6
 template:
 metadata:
 labels:
 app: flags
 spec:
 containers:
 - name: flags
 image: eu.gcr.io/test0/brain:latest
</code></pre>

Get current image of kubernetes deployment

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

如何使用kubectl或API检索容器的当前映像或部署？例如，在使用以下配置创建的部署中，我希望检索值eu.gcr.io/test0/brain:latest。apiVersion: v1   kind: Deployment   metadata:     name: flags   spec:     replicas: 6     template:       metadata:     

问获取当前kubernetes部署的映像
EN

回答 14

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问获取当前kubernetes部署的映像EN

回答 14

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问获取当前kubernetes部署的映像
EN