Pod没有正确回应

时间:2018-05-04 08:22:10

标签: docker kubernetes kubectl kubeadm

我有一个本地(没有云提供商)集群由3 vm主服务器和节点组成,我创建了一个带有nfs的卷,如果一个pod死了并重新安排在另一个节点上,则重用它,但我认为相同组件不能很好地工作:我用这个指南创建集群:kubernetes guide 然后我创建集群这是实际状态:

master@master-VirtualBox:~/Documents/KubeT/nfs$ sudo kubectl get pod --all-namespaces 
    [sudo] password for master: 
    NAMESPACE     NAME                                        READY     STATUS    RESTARTS   AGE
    default       mysqlnfs3                                   1/1       Running   0          27m
    kube-system   etcd-master-virtualbox                      1/1       Running   0          46m
    kube-system   kube-apiserver-master-virtualbox            1/1       Running   0          46m
    kube-system   kube-controller-manager-master-virtualbox   1/1       Running   0          46m
    kube-system   kube-dns-86f4d74b45-f6hpf                   3/3       Running   0          47m
    kube-system   kube-flannel-ds-nffv6                       1/1       Running   0          38m
    kube-system   kube-flannel-ds-rqw9v                       1/1       Running   0          39m
    kube-system   kube-flannel-ds-s5wzn                       1/1       Running   0          44m
    kube-system   kube-proxy-6j7p8                            1/1       Running   0          38m
    kube-system   kube-proxy-7pj8d                            1/1       Running   0          39m
    kube-system   kube-proxy-jqshs                            1/1       Running   0          47m
    kube-system   kube-scheduler-master-virtualbox            1/1       Running   0          46m


master@master-VirtualBox:~/Documents/KubeT/nfs$ sudo kubectl get node
    NAME                STATUS    ROLES     AGE       VERSION
    host1-virtualbox    Ready     <none>    39m       v1.10.2
    host2-virtualbox    Ready     <none>    40m       v1.10.2
    master-virtualbox   Ready     master    48m       v1.10.2

这是pod:

master@master-VirtualBox:~/Documents/KubeT/nfs$ sudo kubectl get pod
    NAME        READY     STATUS    RESTARTS   AGE
    mysqlnfs3   1/1       Running   0          29m

它是在host2上的日程安排,如果我尝试进入主机2的shell并且我做dockerexec我很好地使用容器,数据存储和检索,但是当我尝试使用kubect exec不起作用时:

master@master-VirtualBox:~/Documents/KubeT/nfs$ sudo kubectl exec -it -n default mysqlnfs3 -- /bin/bash
 error: unable to upgrade connection: pod does not exist

0 个答案:

没有答案