Minishift Kubernetes Dashboard throw error: services "kubernetes-dashboard" not found
Minishift Kubernetes Dashboard throw error: services "kubernetes-dashboard" not found
我正在尝试在 MiniShift
内监控我的 pods 的性能,并尝试按照所有说明实施 Kubernetes 仪表板 (https://github.com/kubernetes/dashboard)。
它创建了 Kubernetes-Dashboard 项目(与我试图监控的 NodeJs
项目分开),当我 运行 kubectl
代理并访问 URL (http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard:/proxy/) 它给出了以下错误。
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {
},
"status": "Failure",
"message": "services \"kubernetes-dashboard\" not found",
"reason": "NotFound",
"details": {
"name": "kubernetes-dashboard",
"kind": "services"
},
"code": 404
}
如果您尝试在 minikube
中使用仪表板,情况类似于 minishift。您不需要部署仪表板,因为 minikube
已经集成了对仪表板的支持。
要访问仪表板,请使用以下命令:
minikube dashboard
这将启用仪表板插件,并在默认网络浏览器中打开代理。如果你只想要简单的 url 这里是仪表板命令也可以简单地发出一个 URL:
minikube dashboard --url
回到 minishift,您可能想看看 minishift add-ons and it's kubernetes dashboard add-on
如, you can enable kubernetes dashboard via minikube addons所述:
minikube addons list
minikube addons enable dashboard
# 除了获取有关 CPU/memory/usage 的信息外,请启用 metrics-server
minikube addons enable metrics-server
- 如果您尝试手动安装仪表板,请参阅 docs
1。通过 运行:
应用清单
kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0/aio/deploy/recommended.yaml
2。确保您的部署、服务和相应的端点是由 运行:
部署的
kubectl get all -n kubernetes-dashboard
3。创建 Service Account/ClusterRoleBinding and obtain Bearer Token to access kubernetes dashboard:
注:
IMPORTANT: Make sure that you know what you are doing before proceeding. Granting admin privileges to Dashboard's Service Account might be a security risk
apiVersion: v1
kind: ServiceAccount
metadata:
name: admin-user
namespace: kubernetes-dashboard
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: admin-user
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: cluster-admin
subjects:
- kind: ServiceAccount
name: admin-user
namespace: kubernetes-dashboard
获取不记名令牌:
kubectl -n kubernetes-dashboard describe secret $(kubectl -n kubernetes-dashboard get secret | grep admin-user | awk '{print }')
4。其他资源:
我正在尝试在 MiniShift
内监控我的 pods 的性能,并尝试按照所有说明实施 Kubernetes 仪表板 (https://github.com/kubernetes/dashboard)。
它创建了 Kubernetes-Dashboard 项目(与我试图监控的 NodeJs
项目分开),当我 运行 kubectl
代理并访问 URL (http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard:/proxy/) 它给出了以下错误。
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {
},
"status": "Failure",
"message": "services \"kubernetes-dashboard\" not found",
"reason": "NotFound",
"details": {
"name": "kubernetes-dashboard",
"kind": "services"
},
"code": 404
}
如果您尝试在 minikube
中使用仪表板,情况类似于 minishift。您不需要部署仪表板,因为 minikube
已经集成了对仪表板的支持。
要访问仪表板,请使用以下命令:
minikube dashboard
这将启用仪表板插件,并在默认网络浏览器中打开代理。如果你只想要简单的 url 这里是仪表板命令也可以简单地发出一个 URL:
minikube dashboard --url
回到 minishift,您可能想看看 minishift add-ons and it's kubernetes dashboard add-on
如
minikube addons list
minikube addons enable dashboard
# 除了获取有关 CPU/memory/usage 的信息外,请启用 metrics-server
minikube addons enable metrics-server
- 如果您尝试手动安装仪表板,请参阅 docs
1。通过 运行:
应用清单kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0/aio/deploy/recommended.yaml
2。确保您的部署、服务和相应的端点是由 运行:
部署的kubectl get all -n kubernetes-dashboard
3。创建 Service Account/ClusterRoleBinding and obtain Bearer Token to access kubernetes dashboard:
注:
IMPORTANT: Make sure that you know what you are doing before proceeding. Granting admin privileges to Dashboard's Service Account might be a security risk
apiVersion: v1
kind: ServiceAccount
metadata:
name: admin-user
namespace: kubernetes-dashboard
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: admin-user
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: cluster-admin
subjects:
- kind: ServiceAccount
name: admin-user
namespace: kubernetes-dashboard
获取不记名令牌:
kubectl -n kubernetes-dashboard describe secret $(kubectl -n kubernetes-dashboard get secret | grep admin-user | awk '{print }')
4。其他资源: