如何用一个代理在中层dc/os上成功运行kubernetes?

lyr7nygr  于 2021-06-26  发布在  Mesos
关注(0)|答案(1)|浏览(333)

我正在尝试使用dcos vagrant在只有一个私有代理的中间层dc/os上安装kubernetes。
但是,“kube-node-0”的步骤被卡在“prepared”上:


# dcos kubernetes plan show deploy

deploy (serial strategy) (IN_PROGRESS)
├─ etcd (serial strategy) (COMPLETE)
│  └─ etcd-0:[peer] (COMPLETE)
├─ apiserver (dependency strategy) (COMPLETE)
│  └─ kube-apiserver-0:[instance] (COMPLETE)
├─ mandatory-addons (serial strategy) (COMPLETE)
│  ├─ mandatory-addons-0:[additional-cluster-role-bindings] (COMPLETE)
│  ├─ mandatory-addons-0:[kubelet-tls-bootstrapping] (COMPLETE)
│  ├─ mandatory-addons-0:[kube-dns] (COMPLETE)
│  ├─ mandatory-addons-0:[metrics-server] (COMPLETE)
│  ├─ mandatory-addons-0:[dashboard] (COMPLETE)
│  └─ mandatory-addons-0:[ark] (COMPLETE)
├─ kubernetes-api-proxy (dependency strategy) (COMPLETE)
│  └─ kubernetes-api-proxy-0:[install] (COMPLETE)
├─ controller-manager (dependency strategy) (COMPLETE)
│  └─ kube-controller-manager-0:[instance] (COMPLETE)
├─ scheduler (dependency strategy) (COMPLETE)
│  └─ kube-scheduler-0:[instance] (COMPLETE)
├─ node (dependency strategy) (IN_PROGRESS)
│  └─ kube-node-0:[kube-proxy, coredns, kubelet] (PREPARED)
└─ public-node (dependency strategy) (COMPLETE)

我不理解这个问题,因为还有足够的资源,正如我们在dc/os Jmeter 板上看到的:

以下是kubernete在options.js中的配置:

{
  "kubernetes": {
     "node_count": 1,
     "reserved_resources": {
     "kube_cpus": 10,
     "kube_mem": 10000,
     "kube_disk": 15000
    }
  }
}

下面是vagrantconfig.yaml:

m1:
  ip: 192.168.65.90
  cpus: 2
  memory: 2048
  type: master
a1:
  ip: 192.168.65.111
  cpus: 14
  memory: 13144
  memory-reserved: 512
  type: agent-private
p1:
  ip: 192.168.65.60
  cpus: 2
  memory: 1536
  memory-reserved: 512
  type: agent-public
  aliases:
  - spring.acme.org
  - oinker.acme.org
boot:
  ip: 192.168.65.50
  cpus: 2
  memory: 1024
  type: boot
9w11ddsr

9w11ddsr1#

问题似乎是您为kubernetes节点请求了多少ram。显然,集群的可用ram不足10000mb(根据屏幕截图,10GB中使用了4GB)。作为一个测试,减少到8000,它应该工作。

相关问题