搭建K8S 的dashboard的坑the server could not find the requested resource

搭建K8S 的dashboard的时候显示404
the server could not find the requested resource
如图所示

然后日志文件是这个样子的

Oct 17 03:40:04 k8s-node2 journal: 2019/10/17 07:40:04 No metric client provided. Skipping metrics.
Oct 17 03:40:04 k8s-node2 journal: 2019/10/17 07:40:04 Getting pod metrics
Oct 17 03:40:04 k8s-node2 journal: 2019/10/17 07:40:04 No metric client provided. Skipping metrics.
Oct 17 03:40:04 k8s-node2 journal: 2019/10/17 07:40:04 No metric client provided. Skipping metrics.
Oct 17 03:40:04 k8s-node2 journal: 2019/10/17 07:40:04 No metric client provided. Skipping metrics.
Oct 17 03:40:08 k8s-node2 journal: 2019/10/17 07:40:08 [2019-10-17T07:40:08Z] Incoming HTTP/1.1 GET /api/v1/login/status request from 172.16.88.0:33056: {}
Oct 17 03:40:08 k8s-node2 journal: 2019/10/17 07:40:08 [2019-10-17T07:40:08Z] Outcoming response to 172.16.88.0:33056 with 200 status code
Oct 17 03:40:08 k8s-node2 journal: 2019/10/17 07:40:08 [2019-10-17T07:40:08Z] Incoming HTTP/1.1 GET /api/v1/overview?filterBy=&itemsPerPage=10&name=&page=1&sortBy=d%!C(MISSING)creationTimestamp request from 172.16.88.0:33056: {}
Oct 17 03:40:08 k8s-node2 journal: 2019/10/17 07:40:08 Getting config category
Oct 17 03:40:08 k8s-node2 journal: 2019/10/17 07:40:08 Getting discovery and load balancing category
Oct 17 03:40:08 k8s-node2 journal: 2019/10/17 07:40:08 Getting lists of all workloads
Oct 17 03:40:08 k8s-node2 journal: 2019/10/17 07:40:08 the server could not find the requested resource
Oct 17 03:40:08 k8s-node2 journal: 2019/10/17 07:40:08 [2019-10-17T07:40:08Z] Outcoming response to 172.16.88.0:33056 with 404 status code
Oct 17 03:40:08 k8s-node2 journal: 2019/10/17 07:40:08 No metric client provided. Skipping metrics.
Oct 17 03:40:08 k8s-node2 journal: 2019/10/17 07:40:08 No metric client provided. Skipping metrics.
Oct 17 03:40:08 k8s-node2 journal: 2019/10/17 07:40:08 No metric client provided. Skipping metrics.
Oct 17 03:40:08 k8s-node2 journal: 2019/10/17 07:40:08 Getting pod metrics
Oct 17 03:40:08 k8s-node2 journal: 2019/10/17 07:40:08 No metric client provided. Skipping metrics.
Oct 17 03:40:12 k8s-node2 journal: 2019/10/17 07:40:12 [2019-10-17T07:40:12Z] Incoming HTTP/1.1 GET /api/v1/login/status request from 172.16.88.0:33056: {}
Oct 17 03:40:12 k8s-node2 journal: 2019/10/17 07:40:12 [2019-10-17T07:40:12Z] Outcoming response to 172.16.88.0:33056 with 200 status code
Oct 17 03:40:12 k8s-node2 journal: 2019/10/17 07:40:12 [2019-10-17T07:40:12Z] Incoming HTTP/1.1 GET /api/v1/overview?filterBy=&itemsPerPage=10&name=&page=1&sortBy=d%!C(MISSING)creationTimestamp request from 172.16.88.0:33056: {}
Oct 17 03:40:12 k8s-node2 journal: 2019/10/17 07:40:12 Getting config category
Oct 17 03:40:12 k8s-node2 journal: 2019/10/17 07:40:12 Getting discovery and load balancing category
Oct 17 03:40:12 k8s-node2 journal: 2019/10/17 07:40:12 Getting lists of all workloads
Oct 17 03:40:12 k8s-node2 journal: 2019/10/17 07:40:12 the server could not find the requested resource
Oct 17 03:40:12 k8s-node2 journal: 2019/10/17 07:40:12 [2019-10-17T07:40:12Z] Outcoming response to 172.16.88.0:33056 with 404 status code
Oct 17 03:40:12 k8s-node2 journal: 2019/10/17 07:40:12 No metric client provided. Skipping metrics.
Oct 17 03:40:12 k8s-node2 journal: 2019/10/17 07:40:12 No metric client provided. Skipping metrics.
Oct 17 03:40:12 k8s-node2 journal: 2019/10/17 07:40:12 Getting pod metrics
Oct 17 03:40:12 k8s-node2 journal: 2019/10/17 07:40:12 No metric client provided. Skipping metrics.
Oct 17 03:40:12 k8s-node2 journal: 2019/10/17 07:40:12 No metric client provided. Skipping metrics.
Oct 17 03:40:16 k8s-node2 journal: 2019/10/17 07:40:16 [2019-10-17T07:40:16Z] Incoming HTTP/1.1 GET /api/v1/login/status request from 172.16.88.0:33056: {}
Oct 17 03:40:16 k8s-node2 journal: 2019/10/17 07:40:16 [2019-10-17T07:40:16Z] Outcoming response to 172.16.88.0:33056 with 200 status code
Oct 17 03:40:16 k8s-node2 journal: 2019/10/17 07:40:16 [2019-10-17T07:40:16Z] Incoming HTTP/1.1 GET /api/v1/overview?filterBy=&itemsPerPage=10&name=&page=1&sortBy=d%!C(MISSING)creationTimestamp request from 172.16.88.0:33056: {}
Oct 17 03:40:16 k8s-node2 journal: 2019/10/17 07:40:16 Getting config category
Oct 17 03:40:16 k8s-node2 journal: 2019/10/17 07:40:16 Getting discovery and load balancing category
Oct 17 03:40:16 k8s-node2 journal: 2019/10/17 07:40:16 Getting lists of all workloads
Oct 17 03:40:16 k8s-node2 journal: 2019/10/17 07:40:16 the server could not find the requested resource
Oct 17 03:40:16 k8s-node2 journal: 2019/10/17 07:40:16 [2019-10-17T07:40:16Z] Outcoming response to 172.16.88.0:33056 with 404 status code
Oct 17 03:40:16 k8s-node2 journal: 2019/10/17 07:40:16 No metric client provided. Skipping metrics.
Oct 17 03:40:16 k8s-node2 journal: 2019/10/17 07:40:16 No metric client provided. Skipping metrics.
Oct 17 03:40:16 k8s-node2 journal: 2019/10/17 07:40:16 No metric client provided. Skipping metrics.
Oct 17 03:40:16 k8s-node2 journal: 2019/10/17 07:40:16 Getting pod metrics
Oct 17 03:40:16 k8s-node2 journal: 2019/10/17 07:40:16 No metric client provided. Skipping metrics.
Oct 17 03:40:20 k8s-node2 journal: 2019/10/17 07:40:20 [2019-10-17T07:40:20Z] Incoming HTTP/1.1 GET /api/v1/login/status request from 172.16.88.0:33056: {}
Oct 17 03:40:20 k8s-node2 journal: 2019/10/17 07:40:20 [2019-10-17T07:40:20Z] Outcoming response to 172.16.88.0:33056 with 200 status code
Oct 17 03:40:20 k8s-node2 journal: 2019/10/17 07:40:20 [2019-10-17T07:40:20Z] Incoming HTTP/1.1 GET /api/v1/overview?filterBy=&itemsPerPage=10&name=&page=1&sortBy=d%!C(MISSING)creationTimestamp request from 172.16.88.0:33056: {}
Oct 17 03:40:20 k8s-node2 journal: 2019/10/17 07:40:20 Getting config category
Oct 17 03:40:20 k8s-node2 journal: 2019/10/17 07:40:20 Getting discovery and load balancing category
Oct 17 03:40:20 k8s-node2 journal: 2019/10/17 07:40:20 Getting lists of all workloads
Oct 17 03:40:20 k8s-node2 journal: 2019/10/17 07:40:20 the server could not find the requested resource
Oct 17 03:40:20 k8s-node2 journal: 2019/10/17 07:40:20 [2019-10-17T07:40:20Z] Outcoming response to 172.16.88.0:33056 with 404 status code
Oct 17 03:40:20 k8s-node2 journal: 2019/10/17 07:40:20 No metric client provided. Skipping metrics.
Oct 17 03:40:20 k8s-node2 journal: 2019/10/17 07:40:20 No metric client provided. Skipping metrics.
Oct 17 03:40:20 k8s-node2 journal: 2019/10/17 07:40:20 No metric client provided. Skipping metrics.
Oct 17 03:40:20 k8s-node2 journal: 2019/10/17 07:40:20 Getting pod metrics
Oct 17 03:40:20 k8s-node2 journal: 2019/10/17 07:40:20 No metric client provided. Skipping metrics.

求大神告诉我怎么解决的

docker.service 我配置了
iptables 我配置了
节点上的对应容器也起来了

（已解决）
在官网上下载beta 版本的就可以了！！！！！！！！！

搭建K8S 的dashboard的坑the server could not find the requested resource相关推荐

kubectl报错error validating data: the server could not find the requested resource
使用跳板机执行kubectl 命令报错 kubectl --kubeconfig /root/.kube/config --context kubernetes-admin@kubernetes ap ...
搭建K8S dashboard
书接上文:Centos7.9 从0到1搭建 K8S集群_u011663693的博客-CSDN博客本文记录自己从新建的centos7.9虚拟机搭建K8S集群的心路历程https://blog.csdn. ...
『中级篇』Minikube快速搭建K8S单节点环境（61）
原创文章,欢迎转载.转载请注明:转载自IT人故事会,谢谢! 原文链接地址:『中级篇』Minikube快速搭建K8S单节点环境(61) 去介绍k8s的集群安装,本地搭建一个k8s的集群. 不会科学上网的 ...
k8s部署dashboard
1.dashboard概述 Dashboard是基于网页的Kubernetes用户界面.您可以使用Dashboard将容器应用部署到Kubernetes集群中,也可以对容器应用排错,还能管理集群资源. ...
企业级rancher搭建Kubernetes（采用rancher管理平台搭建k8s）
一.简介 Rancher简介来源官方:https://www.cnrancher.com/ Rancher是一个开源的企业级容器管理平台.通过Rancher,企业再也不必自己使用一系列的开源软件去从 ...
Kubernetes教程之跟着官方文档从零搭建K8S
本文将带领读者一起, 参照着 Kubernetes 官方文档,对其安装部署进行讲解.Kubernetes更新迭代很快,书上.网上等教程可能并不能适用于新版本,但官方文可以. Kubernetes 教程 ...
Redmine3.3.3 搭建与不完全填坑指南
为什么80%的码农都做不了架构师?>>> Redmine3.3.3 搭建与不完全填坑指南 [TOC] 概要 Redmine3.3.3 搭建.不完全填坑指南.不联网安装.Wind ...
Kubeadm 快速搭建 k8s v1.24.1 集群（openEuler 22.03 LTS）
kubeadm 简介 kubeadm 是 Kubernetes(以下简称 k8s)官方提供的用于快速安装部署 k8s 集群的工具,伴随 k8s 每个版本的发布都会同步更新,kubeadm 会对集群配置 ...
hualinux 进阶 1.7：kubeadm1.19搭建k8s群集（最详细的手把手版）
目录一.环境说明 1.1常用问答 1.2 实验目标 1.3 相关配置说明 1.3.1关闭selinux 1.3.2关闭防火墙 1.3.3 时间同步 1.3.4 安装常用软件 1.3.5 安装epel ...

搭建K8S 的dashboard的坑the server could not find the requested resource

搭建K8S 的dashboard的坑the server could not find the requested resource相关推荐

最新文章

热门文章