blocks|key|741052|text|我正在处理我的YAML对象文件，以前，我把每个对象都放在一个单独的文件中，最近我注意到对于一个“部署”对象文件，我有以下的链接警告：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|741053|One+or+more+containers+do+not+have+resource+limits+-+this+could+starve+other+processes|offset|length|style|CODE|741054|在解决这个问题之前，我决定稍微重构一下我的对象定义，并在一个文件中定义多个对象(如果它们是相关的)。所以现在我有了和以前一样的部署，还有卷声明和服务，所有东西都在同一个文件中。|741055|但是，我注意到，部署时没有显示linting警告，但是如果我从文件中删除服务和卷声明，那么它就会显示出来，而不需要部署。|741056|因此，我认为linting代码没有考虑到每个文件定义多个对象的可能性。|741057|谢谢!|741058|entityMap^0|0|0|2E|0|0|0|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|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|Y|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|Q|$]]

I was working with my YAML object files and previously I have every single object in a separated file and I recently noticed that for a &quot;Deployment&quot; object file I have the following linting warning:
<code>One or more containers do not have resource limits - this could starve other processes</code>
Before fixing that issue, I decided to refactor my object definition a bit and define more than one object in a single file if they are related. So now I have the same Deployment as before along with a Volume Claim and a Service, everything in the same file.
But then I noted that the linting warning doesn't show up for the Deployment, but it does show up if I delete the Service and Volume Claim from the file, leaving the Deployment alone.
So I suppose the linting code is not taking into account the possibility of having many objects definition per file.
Thanks!

blocks|key|741070|text|声明每个容器的内存和cpu的资源请求和限制是一种很好的做法。这有助于将容器调度到有Pod可用资源的节点上，并且使Pod不使用其他Pods所需的资源--因此，“这可能会导致其他进程饥饿”消息。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|741071|向示例添加资源请求和限制|741072|apiVersion:+v1
kind:+Pod
metadata:
++name:+myapp-pod
++labels:+
++++app:+myapp
++++type:+server
spec:
++containers:
++-+name:+nginx-container
++++image:+nginx
++++resources:
++++++limits:
++++++++memory:+512Mi
++++++++cpu:+"1"
++++++requests:
++++++++memory:+256Mi
++++++++cpu:+"0.2"|code-block|syntax|javascript|741073|entityMap|0|LINK|mutability|MUTABLE|url|https://kubernetes.io/docs/tasks/configure-pod-container/assign-memory-resource/|1|https://kubernetes.io/docs/tasks/configure-pod-container/assign-cpu-resource/^0|7|2|0|A|3|1|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]|$A|Y|B|Z|1|10]]|C|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|12|8|@]|9|@]|C|$I|J]]|$1|K|3|-4|5|6|7|13|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]|S|$5|N|O|P|C|$Q|T]]]]

It is a good practice to declare resource requests and limits for both <a href="https://kubernetes.io/docs/tasks/configure-pod-container/assign-memory-resource/" rel="noreferrer">memory</a> and <a href="https://kubernetes.io/docs/tasks/configure-pod-container/assign-cpu-resource/" rel="noreferrer">cpu</a> for each container. This helps to schedule the container to a node that has available resources for your Pod, and also so that your Pod does not use resources that other Pods needs - therefore the &quot;this could starve other processes&quot; message.
E.g. to add resource requests and limits to your example
<pre><code>apiVersion: v1
kind: Pod
metadata:
 name: myapp-pod
 labels: 
 app: myapp
 type: server
spec:
 containers:
 - name: nginx-container
 image: nginx
 resources:
 limits:
 memory: 512Mi
 cpu: &quot;1&quot;
 requests:
 memory: 256Mi
 cpu: &quot;0.2&quot;
</code></pre>

blocks|key|124926|text|如您所知，该警告来自VS代码扩展ms-kubernetes-tools.vscode-kubernetes-tools中的linter。如果希望链接器禁用警告|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|124927|One+or+more+containers+do+not+have+resource+limits+-+this+could+starve+other+processes|code-block|syntax|javascript|124928|然后编辑VS代码setting.json如下所示：|124929|{
++++"vs-kubernetes":+{
++++++++"disable-linters":+["resource-limits"],
++++++++...
++++},
++++...
}|124930|entityMap^0|G|17|0|0|8|C|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$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|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|P|$]]

As you know, that warning comes from the linter in VS Code Extension <code>ms-kubernetes-tools.vscode-kubernetes-tools</code>. If you want the linter to disable the warning
<pre><code>One or more containers do not have resource limits - this could starve other processes
</code></pre>
then edit VS Code <code>setting.json</code> to look like this:
<pre><code>{
 &quot;vs-kubernetes&quot;: {
 &quot;disable-linters&quot;: [&quot;resource-limits&quot;],
 ...
 },
 ...
}
</code></pre>

After creating the pod-definition.yml file.
<pre><code>apiVersion: v1
kind: Pod
metadata:
 name: myapp-pod
 labels: 
 app: myapp
 type: server
spec:
 containers:
 - name: nginx-container
 image: nginx
</code></pre>
The linter is giving this warning.
<code>One or more containers do not have resource limits - this could starve other processes</code>

One or more containers do not have resource limits - warning in VS Code Kubernetes tools

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

在创建po-finition.yml文件之后。apiVersion: v1kind: Podmetadata:    name: myapp-pod    labels:       app: myapp      type: serverspec:    containers:        - name: ngin...

问一个或多个容器没有资源限制-在VS代码Kubernetes工具中警告
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问一个或多个容器没有资源限制-在VS代码Kubernetes工具中警告EN