blocks|key|111415|text|要解决这个问题，请降低客户端的级别或升级服务器。在我的例子中，我升级了服务器(新的minikube)，但是忘记了升级客户端(kubectl)并最终得到了这些版本。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|111416|$+kubectl+version+--short
Client+Version:+v1.9.0
Server+Version:+v1.14.1|code-block|syntax|javascript|111417|当我将客户端版本升级(在本例中为1.14.2)时，一切又开始工作了。|111418|关于如何安装(在您的例子中是升级)客户端的说明如下：https://kubernetes.io/docs/tasks/tools/install-kubectl|offset|length|111419|entityMap|0|LINK|mutability|MUTABLE|url|https://kubernetes.io/docs/tasks/tools/install-kubectl^0|0|0|0|Q|1I|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|X|8|@]|9|@$K|Y|L|Z|1|10]]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

To solve this, downgrade the client or upgrade the server. In my case I've upgraded server (new minikube) but forget to upgrade client (kubectl) and end up with those versions.
<pre><code>$ kubectl version --short
Client Version: v1.9.0
Server Version: v1.14.1
</code></pre>
When I'd upgraded client version (in this case to 1.14.2) then everything started to work again.
Instructions how to install (in your case upgrade) client are here <a href="https://kubernetes.io/docs/tasks/tools/install-kubectl" rel="nofollow noreferrer">https://kubernetes.io/docs/tasks/tools/install-kubectl</a>

blocks|key|111398|text|在尝试使用Jenkins和Kubernetes制作CD时，我也犯了同样的错误。在这个过程中，我导出了kubectl+create+-f+app-deployment.yml+-v=8，这个图像显示了关于错误的更多信息：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|111399|​|111400|📷|atomic|111401|111402|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/5931c57c37d5a72c3f66e8e8c0e4fff0.png|imageAlt^0|5|7|D|A|1E|15|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@$9|W|A|X|B|C]|$9|Y|A|Z|B|C]|$9|10|A|11|B|D]]|E|@]|F|$]]|$1|G|3|H|5|6|7|12|8|@]|E|@]|F|$]]|$1|I|3|J|5|K|7|13|8|@]|E|@$9|14|A|15|1|16]]|F|$]]|$1|L|3|H|5|6|7|17|8|@]|E|@]|F|$]]|$1|M|3|-4|5|6|7|18|8|@]|E|@]|F|$]]]|N|$O|$5|P|Q|R|F|$S|T|U|-4]]]]

I have the same error when trying to do a CD with Jenkins and Kubernetes. In the pipeline I excute <code>kubectl create -f app-deployment.yml -v=8</code> This image show more information about the error:

<a href="https://i.stack.imgur.com/NA0Te.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/NA0Te.png" alt="enter image description here"></a>

blocks|key|111292|text|版本问题的原因：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|111293|来自文档|offset|length|111294|客户端不应超过一个主版本的次要版本，但可能导致主版本最多为一个次要版本。例如，v1.3主服务器应该与v1.1、v1.2和v1.3节点一起工作，并且应该与v1.2、v1.3和v1.4客户端一起工作。|blockquote|111295|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/kubernetes/community/blob/master/contributors/design-proposals/release/versioning.md#supported-releases-and-component-skew^0|0|2|2|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@$D|S|E|T|1|U]]|A|$]]|$1|F|3|G|5|H|7|V|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P]]]]

The cause of problem in versions:

From <a href="https://github.com/kubernetes/community/blob/master/contributors/design-proposals/release/versioning.md#supported-releases-and-component-skew" rel="nofollow noreferrer">documentation</a>

<blockquote>
 a client should be skewed no more than one minor version from the
 master, but may lead the master by up to one minor version. For
 example, a v1.3 master should work with v1.1, v1.2, and v1.3 nodes,
 and should work with v1.2, v1.3, and v1.4 clients.
</blockquote>

blocks|key|111312|text|来自http://words.yuvi.in/post/kubectl-rbac/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|111313|运行kubectl+create+-f+notRelevantToThisQuestion.yml+-v=8将打印所有HTTP流量(请求和响应！)以一种容易理解的方式。通过这种方式，可以从http响应中识别哪些资源不可用。|style|CODE|111314|entityMap|0|LINK|mutability|MUTABLE|url|http://words.yuvi.in/post/kubectl-rbac/^0|2|13|0|0|2|1G|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@$A|U|B|V|F|G]]|9|@]|C|$]]|$1|H|3|-4|5|6|7|W|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

From <a href="http://words.yuvi.in/post/kubectl-rbac/" rel="nofollow noreferrer">http://words.yuvi.in/post/kubectl-rbac/</a>

Running <code>kubectl create -f notRelevantToThisQuestion.yml -v=8</code> will print all the HTTP traffic (requests and responses!) in an easy to read way. In this way, one can identify which resource is not available from the http responses.

blocks|key|111432|text|应用这些，然后尝试|type|unstyled|depth|inlineStyleRanges|entityRanges|data|111433|mkdir+-p+$HOME/..kube|111434|sudo+-i+/etc/kubernetes/admin.conf+$HOME/..kube/config|111435|sudo+$(id+-u):$(id+-g)+$HOME/..kube/config|111436|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

apply these and then try
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config

blocks|key|955274|text|此解决方案特别适用于mac用户。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|955275|步骤1:更新kubernetes|955276|brew+upgrade+kubernetes-cli|code-block|syntax|javascript|955277|第二步：-覆盖它|955278|brew+link+--overwrite+kubernetes-cli|955279|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

This solution is particularly for mac users.
Step 1:- Update kubernetes
<pre><code>brew upgrade kubernetes-cli
</code></pre>
Step 2:- Overwrite it
<pre><code>brew link --overwrite kubernetes-cli
</code></pre>

blocks|key|2188903|text|对于Openshift，在更新到最新的oc+CLI之后，我使用了旧的oc+CLI版本，解决了我的问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2188904|entityMap^0|2|9|D|C|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

For Openshift, I was using old oc CLI version, after updating to latest oc CLI solved my issue

blocks|key|111555|text|在从仪表板创建资源时，我偶然发现了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|111556|资源是命名空间，我没有选择名称空间。选择命名空间固定的the+server+could+not+find+the+requested+resource错误。|offset|length|style|CODE|111557|​|111558|📷|atomic|111559|111560|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/0176bb874fe46b35933a4775770e9987.png|imageAlt^0|0|R|1C|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|11|8|@]|9|@$D|12|E|13|1|14]]|A|$]]|$1|M|3|I|5|6|7|15|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U|V|-4]]]]

I stumbled upon this question when creating resource from Dashboard.
The resource was namespaced and I had no namespace selected. Selecting namespace fixed <code>the server could not find the requested resource</code> error.
<a href="https://i.stack.imgur.com/1gWb0.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/1gWb0.png" alt="k8s dashboard" /></a>

blocks|key|955374|text|在我的例子中，我没有启用来自docker桌面的kubernetes。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|955375|我让它起作用了。|955376|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

In my case, I didn't enable kubernetes from docker desktop.
I enabled it which worked.

I'm running <code>kubectl create -f notRelevantToThisQuestion.yml</code>

The response I get is:

<blockquote>
 Error from server (NotFound): the server could not find the requested
 resource
</blockquote>

Is there any way to determine which resource was requested that was not found?

<code>kubectl get ns</code> returns

<blockquote>
 NAME STATUS AGE default Active 243d 
 kube-public Active 243d kube-system Active 243d 
</blockquote>

This is not a cron job. 
Client version 1.9 
Server version 1.6

This is very similar to <a href="https://devops.stackexchange.com/questions/2956/how-do-i-get-kubernetes-to-work-when-i-get-an-error-the-server-could-not-find-t?rq=1">https://devops.stackexchange.com/questions/2956/how-do-i-get-kubernetes-to-work-when-i-get-an-error-the-server-could-not-find-t?rq=1</a> but my k8s cluster has been deployed correctly (everything's been working for almost a year, I'm adding a new pod now).

Determine what resource was not found from "Error from server (NotFound): the server could not find the requested resource"

33 天实现自己的 AI 进化论？发文瓜分机械键盘、耳机等万元奖池！点击参加活动：<a href="https://cloud.tencent.com/developer/article/2503022" target="_blank">https://cloud.tencent.com/developer/article/2503022</a> 
 <img src="https://qcloudimg.tencent-cloud.cn/raw/01543e0407db10898a7ee9f420794432.jpg"/>

技术创作特训营有奖征文

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

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

腾讯云数据库专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云AI代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

我在运行kubectl create -f notRelevantToThisQuestion.yml我得到的回应是：来自服务器的错误(NotFound)：服务器找不到请求的资源是否有任何方法来确定哪些资源被请求而没有被找到？kubectl get ns返回姓名状态年龄默认活动243dkube-公共活动24dkube-系统活性243d这不是一份工作。客户版本1.9服务器版本1.6这与非常相似，但我

问确定从“(NotFound)：服务器找不到所请求的资源”中找不到什么资源
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问确定从“(NotFound)：服务器找不到所请求的资源”中找不到什么资源EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问确定从“(NotFound)：服务器找不到所请求的资源”中找不到什么资源
EN