Suj*_*jee 2 kubernetes kubernetes-dashboard kubernetes-cluster
我已经在集群上部署了 Kubernetes Dashboard,并且能够使用 kubectl 代理访问仪表板。
但是当我尝试使用 URL 通过浮动 IP/VIP 访问仪表板时:
https://<FloatingIP>:6443/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login
Run Code Online (Sandbox Code Playgroud)
我最终在浏览器上得到以下响应
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {
},
"status": "Failure",
"message": "services \"https:kubernetes-dashboard:\" is forbidden: User \"system:anonymous\" cannot get resource \"services/proxy\" in API group \"\" in the namespace \"kube-system\"",
"reason": "Forbidden",
"details": {
"name": "https:kubernetes-dashboard:",
"kind": "services"
},
"code": 403
}
Run Code Online (Sandbox Code Playgroud)
我确实知道这个问题是由于 Kubernetes 上的 RBAC 造成的,并围绕这个主题做了一些阅读,但我仍然不清楚需要做什么来解决主集群实现上的这个问题。我能够在单个主服务器上成功公开仪表板 - 具有 NodePort 访问权限的多节点设置,但是使用集群主设置会失败。
我也愿意接受在此拓扑中实施仪表板的更好建议。
如果您需要任何其他信息,请告诉我
Han*_* Du 13
您将需要创建一个集群角色来授予 kubernetes-dashboard 的权限并将其绑定到 system:anonymous 用户,如下所示。
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: kubernetes-dashboard-anonymous
rules:
- apiGroups: [""]
resources: ["services/proxy"]
resourceNames: ["https:kubernetes-dashboard:"]
verbs: ["get", "list", "watch", "create", "update", "patch", "delete"]
- nonResourceURLs: ["/ui", "/ui/*", "/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/*"]
verbs: ["get", "list", "watch", "create", "update", "patch", "delete"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: kubernetes-dashboard-anonymous
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: kubernetes-dashboard-anonymous
subjects:
- kind: User
name: system:anonymous
Run Code Online (Sandbox Code Playgroud)
编辑: 要应用这些更改,请将其保存到 .yaml(例如:clusterrole.yaml)文件中并运行
kubectl apply -f clusterrole.yaml
Run Code Online (Sandbox Code Playgroud)
| 归档时间: |
|
| 查看次数: |
3836 次 |
| 最近记录: |