我已经安装了kubernetes试用版,并在我的桌面上运行了ubuntu。然而,提出吊舱似乎有一些问题。Kubectl获取所有名称空间,显示处于ContainerCreating状态的所有豆荚,并且没有转移到就绪状态。
即使当我做库伯内特斯-仪表板时,我也得到了
等待,服务端点尚未准备好。
Minikube版本: v0.20.0
环境:
我在Ubuntu上安装了minikube和kubectl。但是,我不能通过CLI和GUI访问仪表板。
http://127.0.0.1:8001/ui给出以下错误
{ "kind": "Status", "apiVersion": "v1", "metadata": {}, "status": "Failure", "message": "no endpoints available for service "kubernetes-dashboard"", "reason": "ServiceUnavailable", "code": 503 }
而CLI上的minikube仪表板不打开仪表板: Output
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
.......
Could not find finalized endpoint being pointed to by kubernetes-dashboard: Temporary Error: Endpoint for service is not ready yet
Temporary Error: Endpoint for service is not ready yet
Temporary Error: Endpoint for service is not ready yet
Temporary Error: Endpoint for service is not ready yet
kubectl版本:Client Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.0", GitCommit:"d3ada0119e776222f11ec7945e6d860061339aad", GitTreeState:"clean", BuildDate:"2017-06-29T23:15:59Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.4", GitCommit:"d6f433224538d4f9ca2f7ae19b252e6fcb66a3ae", GitTreeState:"dirty", BuildDate:"2017-06-22T04:31:09Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}
minikube日志还报告了以下错误:
Jul 10 08:46:12 minikube localkube[3237]: I0710 08:46:12.901880 3237 kuberuntime_manager.go:458] Container {Name:php-redis Image:gcr.io/google-samples/gb-frontend:v4 Command:[] Args:[] WorkingDir: Ports:[{Name: HostPort:0 ContainerPort:80 Protocol:TCP HostIP:}] EnvFrom:[] Env:[{Name:GET_HOSTS_FROM Value:dns ValueFrom:nil}] Resources:{Limits:map[] Requests:map[cpu:{i:{value:100 scale:-3} d:{Dec:} s:100m Format:DecimalSI} memory:{i:{value:104857600 scale:0} d:{Dec:} s:100Mi Format:BinarySI}]} VolumeMounts:[{Name:default-token-gqtvf ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath:}] LivenessProbe:nil ReadinessProbe:nil Lifecycle:nil TerminationMessagePath:/dev/termination-log TerminationMessagePolicy:File ImagePullPolicy:IfNotPresent SecurityContext:nil Stdin:false StdinOnce:false TTY:false} is dead, but RestartPolicy says that we should restart it. Jul 10 08:46:14 minikube localkube[3237]: E0710 08:46:14.139555 3237 remote_runtime.go:86] RunPodSandbox from runtime service failed: rpc error: code = 2 desc = unable to pull sandbox image "gcr.io/google_containers/pause-amd64:3.0": Error response from daemon: Get https://gcr.io/v1/_ping: x509: certificate signed by unknown authority ....
名称:kubernetes-仪表板-2039414953-czptd命名空间: kube-system Node: minikube/192.168.99.102启动时间: Fri,2017年7月14日09:31:58 +0530标签: k8s-app=kubernetes-dashboard pod-散列=2039414953注释: kubernetes.io/created-by={"kind":"SerializedReference","apiVersion":"v1",“引用”:{“样”:“ReplicaSet”,“命名空间”:“kube-system”,"name":"kubernetes-dashboard-2039414953",“uid”:“2eb39682-6849-11e7-8.状态:未决IP:由:ReplicaSet/kubernetes-仪表板-2039414953创建,控制为:ReplicaSet/kubernetes-仪表板-2039414953容器: kubernetes-仪表板:容器ID:图像: gcr.io/google_containers/kubernetes-dashboard-amd64:v1.6.1图像ID: 端口: 9090/TCP状态:等待原因: ContainerCreating就绪:错误重新启动计数:0活性:http-获取http://:9090/ delay=30s timeout=30s period=10s #success=1 #failure=3 #failure=3环境:挂载:/var/run/机密/kubernetes.io/serviceaccount来自kubernetes-仪表板-令牌-12 get (ro)条件:类型状态 初始化True就绪假PodScheduled真卷: SecretName: kubernetes-dashboard-12 node: Type: QoS : BestEffort -role.kubernetes.io/master:BestEffort 来自FirstSeen类型原因消息的LastSeen计数 跳过:"kubernetes-dashboard-2039414953-czptd_kube-system(2eb57d9b-6849-11e7-8a56-080027206461)“的"CreatePodSandbox”,CreatePodSandboxError:"CreatePodSandbox for pod \"kubernetes-dashboard-2039414953-czptd_kube-system(2eb57d9b-6849-11e7-8a56-080027206461)\“failed: rpc错误: code =2 desc =无法提取沙箱图像\”gcr.io/google_containers/\“kubernetes-dashboard-2039414953-czptd_kube-system(2eb57d9b-6849-11e7-8a56-080027206461)\”64:3.0\“:来自守护进程的错误响应:获取ping:x509:由未知权威机构签名的证书”
发布于 2017-07-14 05:34:42
很有可能正在下载Pod容器映像。图片不是很大,所以图像应该被下载的相当快,在一个体面的互联网连接。
您可以使用kubectl describe pod --namespace kube-system <pod-name>
来了解有关吊舱启动状态的更多细节。看看输出的Events
部分。
除非kube-system
命名空间中的所有kubernetes组件都处于READY
状态,否则您将无法访问仪表板。
您也可以尝试使用SSH
'ing到带有minikube ssh
的迷你虚拟机中来调试这个问题。
发布于 2017-07-25 03:30:48
我能够通过使用VPN连接来解决这个问题,因为我在公司网络中有限制。这将阻止安装试图提取沙箱映像的站点。
发布于 2017-11-24 16:58:34
试着使用:
kubectl config use-context minikube
..as可能已经启动了预先存在的配置。
https://stackoverflow.com/questions/45004384
复制相似问题