Kubernetes installation stuck in IN_PROGRESS about dcos-kubernetes-quickstart HOT 8 CLOSED

@uditha-atukorala can you try to search for any FAIL offer in the output of https://<CLUSTER_IP>/service/kubernetes/v1/debug/offers ? I believe it is related to lack of enough available resources

from dcos-kubernetes-quickstart.

@hectorj2f, thanks for the pointers. It does look like it is not having enough resources.

e.g.

FAIL(ResourceEvaluationStage): Offer failed to satisfy: name: cpus, value: type: SCALAR scalar { value: 3.0 }, role: kubernetes-role, pre-reserved-role: *, principal: kubernetes-principal with resourceId: Optional.empty

FAIL(VolumeEvaluationStage): Offer failed to satisfy: name: disk, value: type: SCALAR scalar { value: 10240.0 }, role: kubernetes-role, pre-reserved-role: *, principal: kubernetes-principal, type: 'ROOT', container-path: 'var' with resourceId: Optional.empty

I'll take a look.

from dcos-kubernetes-quickstart.

No problem. Closing this issue!

from dcos-kubernetes-quickstart.

Hey @hectorj2f ,
I came across the same issue, Could you please let me know the recommended resources that need to be configured for kube-node such that the kubernetes dashboard works. I tried to scale my resource both horizontally and vertically but still didn't find any luck.I'm trying to install using dcos-vagrant on my local machine.

Thanks in advance

from dcos-kubernetes-quickstart.

Here are the logs from above mentioned url,

FAIL(VolumeEvaluationStage): Offer failed to satisfy: name: disk, value: type: SCALAR scalar { value: 10240.0 }, role: kubernetes-role, pre-reserved-role: *, principal: kubernetes-principal, type: 'ROOT', container-path: 'var' with resourceId: Optional.empty

FAIL(ResourceEvaluationStage): Offer failed to satisfy: name: cpus, value: type: SCALAR scalar { value: 0.1 }, role: kubernetes-role, pre-reserved-role: *, principal: kubernetes-principal with resourceId: Optional.empty

FAIL(ResourceEvaluationStage): Offer failed to satisfy: name: mem, value: type: SCALAR scalar { value: 32.0 }, role: kubernetes-role, pre-reserved-role: *, principal: kubernetes-principal with resourceId: Optional.empty

FAIL(ResourceEvaluationStage): Offer failed to satisfy: name: cpus, value: type: SCALAR scalar { value: 0.1 }, role: kubernetes-role, pre-reserved-role: *, principal: kubernetes-principal with resourceId: Optional.empty

FAIL(ResourceEvaluationStage): Offer failed to satisfy: name: mem, value: type: SCALAR scalar { value: 32.0 }, role: kubernetes-role, pre-reserved-role: *, principal: kubernetes-principal with resourceId: Optional.empty

FAIL(ResourceEvaluationStage): Offer failed to satisfy: name: disk, value: type: SCALAR scalar { value: 256.0 }, role: kubernetes-role, pre-reserved-role: *, principal: kubernetes-principal with resourceId: Optional.empty

PASS(LaunchEvaluationStage): Added launch information to offer requirement

FAIL(ResourceEvaluationStage): Offer failed to satisfy: name: cpus, value: type: SCALAR scalar { value: 0.1 }, role: kubernetes-role, pre-reserved-role: *, principal: kubernetes-principal with resourceId: Optional.empty

FAIL(ResourceEvaluationStage): Offer failed to satisfy: name: mem, value: type: SCALAR scalar { value: 512.0 }, role: kubernetes-role, pre-reserved-role: *, principal: kubernetes-principal with resourceId: Optional.empty

And also dcos kubernetes plan status deploy output:

deploy (serial strategy) (IN_PROGRESS)
├─ etcd (serial strategy) (COMPLETE)
│ └─ etcd-0:[peer] (COMPLETE)
├─ apiserver (parallel strategy) (COMPLETE)
│ └─ kube-apiserver-0:[instance] (COMPLETE)
├─ mandatory-addons (serial strategy) (COMPLETE)
│ ├─ mandatory-addons-0:[additional-cluster-role-bindings] (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 (parallel strategy) (COMPLETE)
│ └─ kubernetes-api-proxy-0:[install] (COMPLETE)
├─ controller-manager (parallel strategy) (COMPLETE)
│ └─ kube-controller-manager-0:[instance] (COMPLETE)
├─ scheduler (parallel strategy) (COMPLETE)
│ └─ kube-scheduler-0:[instance] (COMPLETE)
├─ node (parallel strategy) (IN_PROGRESS)
│ └─ kube-node-0:[kube-proxy, coredns, kubelet] (PREPARED)
└─ public-node (parallel strategy) (COMPLETE)

from dcos-kubernetes-quickstart.

@uditha-atukorala May be you can guide me on this since you already have a solution,

from dcos-kubernetes-quickstart.

@ravinani02 Did you have a look at the docs https://github.com/mesosphere/dcos-kubernetes/blob/master/docs/package/install.md#prerequisites ? Based on the FAIL logs, you shared here, it seems there aren't enough available resources in your cluster.

from dcos-kubernetes-quickstart.

@ravinani02, my issue was not having enough agent node resources. I ended up upgrading my nodes but you can also try scaling the k8s cluster down.

from dcos-kubernetes-quickstart.