Kubernetes:主节点列在'kubectl get po'列表中?



今天从 github 中提取了最新的 kubernetes 代码。

步骤:在一个名为 dpcdd3 的 Ubuntu 服务器上运行 docs/getting-started-guides/docker-multinode/master.sh。或者,这里是网址:

https://github.com/kubernetes/kubernetes/blob/master/docs/getting-started-guides/docker-multinode/master.sh

# kubectl get no
NAME      LABELS                          STATUS    AGE
dpcdd3    kubernetes.io/hostname=dpcdd3   Ready     1h

(注意:worker.sh 尚未在第二台服务器上调用)。

在较旧的代码(大约一个月前随机选择)上,相同的命令,在相同的设置中:"kubectl get no"不会返回任何内容。

以下是一些当前的运行时详细信息:

# kubectl version
Client Version: version.Info{Major:"1", Minor:"2+", GitVersion:"v1.2.0-alpha.6.239+a5d2c1b0fb23a1", GitCommit:"a5d2c1b0fb23a145c47935f041a036d8546cd01f", GitTreeState:"clean"}
Server Version: version.Info{Major:"1", Minor:"1", GitVersion:"v1.1.3", GitCommit:"6a81b50c7e97bbe0ade075de55ab4fa34f049dc2", GitTreeState:"clean"}

有趣的是,豆荚显示状态为:"待处理":

# kubectl get po
NAME                READY     STATUS    RESTARTS   AGE
k8s-master-dpcdd3   0/3       Pending   0          1h

更多细节:

# kubectl describe po 
Name:           k8s-master-dpcdd3
Namespace:      default
Image(s):       gcr.io/google_containers/hyperkube:v1.1.3,gcr.io/google_containers/hyperkube:v1.1.3,gcr.io/google_containers/hyperkube:v1.1.3
Node:           dpcdd3/
Labels:         <none>
Status:         Pending
Reason:
Message:
IP:
Controllers:    <none>
Containers:
  controller-manager:
    Container ID:
    Image:              gcr.io/google_containers/hyperkube:v1.1.3
    Image ID:
    Command:
      /hyperkube
      controller-manager
      --master=127.0.0.1:8080
      --v=2
    QoS Tier:
      cpu:              BestEffort
      memory:           BestEffort
    State:              Waiting
    Ready:              False
    Restart Count:      0
    Environment Variables:
  apiserver:
    Container ID:
    Image:              gcr.io/google_containers/hyperkube:v1.1.3
    Image ID:
    Command:
      /hyperkube
      apiserver
      --portal-net=10.0.0.1/24
      --address=0.0.0.0
      --etcd-servers=http://127.0.0.1:4001
      --cluster-name=kubernetes
      --v=2
    QoS Tier:
      cpu:              BestEffort
      memory:           BestEffort
    State:              Waiting
    Ready:              False
    Restart Count:      0
    Environment Variables:
  scheduler:
    Container ID:
    Image:              gcr.io/google_containers/hyperkube:v1.1.3
    Image ID:
    Command:
      /hyperkube
      scheduler
      --master=127.0.0.1:8080
      --v=2
    QoS Tier:
      cpu:              BestEffort
      memory:           BestEffort
    State:              Waiting
    Ready:              False
    Restart Count:      0
    Environment Variables:
No volumes.
No events.
Namespace:      default

应该是

Namespace:      kube-system

最新更新