我对Kubernetes是完全陌生的,所以请放轻松。
我正在运行image_composite()
,但只看到JSON输出。基于this discussion,我尝试通过运行以下命令来设置内存限制:
kubectl proxy
然后我更改了容器内存限制:
kubectl edit deployment kubernetes-dashboard --namespace kube-system
当我保存并访问http://127.0.0.1:8001/ui
时,仍然只能获得JSON服务正在运行apiVersion: extensions/v1beta1
kind: Deployment
metadata:
...
spec:
...
template:
metadata:
...
spec:
containers:
- image: k8s.gcr.io/kubernetes-dashboard-amd64:v1.8.1
imagePullPolicy: IfNotPresent
livenessProbe:
...
name: kubernetes-dashboard
ports:
- containerPort: 9090
protocol: TCP
resources:
limits:
memory: 1Gi
,我看到以下内容:
kubectl logs --namespace kube-system kubernetes-dashboard-665756d87d-jssd8
我仔细阅读了Google search上的一堆有关该错误的链接,但实际上没有任何作用。
关键组件是:
通过以下方式安装:
Starting overwatch
Using in-cluster config to connect to apiserver
Using service account token for csrf signing
No request provided. Skipping authorization
Successful initial request to the apiserver, version: v1.10.0
Generating JWE encryption key
New synchronizer has been registered: kubernetes-dashboard-key-holder-kube-system. Starting
Starting secret synchronizer for kubernetes-dashboard-key-holder in namespace kube-system
Initializing JWE encryption key from synchronized object
Creating in-cluster Heapster client
Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds.
Serving insecurely on HTTP port: 9090
半路!
答案 0 :(得分:1)
Have you considered using the minikube dashboard? You can reach it by:
minikube dashboard
Also you will get json on http://127.0.0.1:8001/ui,因为它已被弃用,因此您必须使用仪表板github page中陈述的完整代理URL。 / p>
如果您仍然希望将此“外部”仪表板用于将来的与minikube相关的项目,或者我不知道有其他原因可以通过以下方式达到此目的:
kubectl proxy
,然后: http://localhost:8001/api/v1/namespaces/kube-system/services/http:kubernetes-dashboard:/proxy/
https
在这种情况下不正确(可能是文档错误,或者可能在documentation部分中得到了澄清,如果您需要更多信息,我建议您阅读该部分)在网络用户界面上。希望这会有所帮助。