# Unable to setup kubernetes cluster using rancher

**URL:** <https://forums.suse.com/t/unable-to-setup-kubernetes-cluster-using-rancher/21016>\
**Category:** General\
**Created:** [August 26, 2021, 6:26am UTC](https://forums.suse.com/t/unable-to-setup-kubernetes-cluster-using-rancher/21016 "2021-08-26T06:26:29Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rhnapril](https://avatars.discourse-cdn.com/v4/letter/r/7cd45c/32.png) [@rhnapril](https://forums.suse.com/u/rhnapril)\
**Post date:** [August 26, 2021, 6:26am UTC](https://forums.suse.com/t/unable-to-setup-kubernetes-cluster-using-rancher/21016/1 "2021-08-26T06:26:30Z")

</div>

I am trying to create a 1 node kubernetes cluster in a Ubuntu VM installed in a virtual box .

Ubuntu VERSION="20.04.2 LTS

Rancher version - v1.1.19

Docker version - 20.10.7

However i am not able to finish the setup of the cluster , i am getting the below error

FATA[0000] Failed to validate cluster: Address for host (1) is not provided

Could someone please help out

---

<div class="post-metadata">

**Author:** ![superseb](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/superseb/32/2424_2.png) [@superseb](https://forums.suse.com/u/superseb)\
**Post date:** [August 29, 2021, 12:04pm UTC](https://forums.suse.com/t/unable-to-setup-kubernetes-cluster-using-rancher/21016/2 "2021-08-29T12:04:03Z")

</div>

Rancher version v1.1.19? I assume you are using RKE? It is recommended to use the latest version available but it should still work fine. Please share your `cluster.yml`.

---

<div class="post-metadata">

**Author:** ![rhnapril](https://avatars.discourse-cdn.com/v4/letter/r/7cd45c/32.png) [@rhnapril](https://forums.suse.com/u/rhnapril)\
**Post date:** [August 30, 2021, 7:45am UTC](https://forums.suse.com/t/unable-to-setup-kubernetes-cluster-using-rancher/21016/3 "2021-08-30T07:45:43Z")

</div>

Hi ,

sharing my cluster.yml

* * *

# If you intened to deploy Kubernetes in an air-gapped environment,

# please consult the documentation on how to configure custom RKE images.

nodes:

- address: “”  
port: “22”  
internal\_address: “”  
role:
  - controlplane  
hostname\_override: “”  
user: rohan  
docker\_socket: /var/run/docker.sock  
ssh\_key: “”  
ssh\_key\_path: ~/.ssh/id\_rsa  
ssh\_cert: “”  
ssh\_cert\_path: “”  
labels: {}  
taints:   
services:  
etcd:  
image: “”  
extra\_args: {}  
extra\_binds:   
extra\_env:   
win\_extra\_args: {}  
win\_extra\_binds:   
win\_extra\_env:   
external\_urls:   
ca\_cert: “”  
cert: “”  
key: “”  
path: “”  
uid: 0  
gid: 0  
snapshot: null  
retention: “”  
creation: “”  
backup\_config: null  
kube-api:  
image: “”  
extra\_args: {}  
extra\_binds:   
extra\_env:   
win\_extra\_args: {}  
win\_extra\_binds:   
win\_extra\_env:   
service\_cluster\_ip\_range: 10.43.0.0/16  
service\_node\_port\_range: “”  
pod\_security\_policy: false  
always\_pull\_images: false  
secrets\_encryption\_config: null  
audit\_log: null  
admission\_configuration: null  
event\_rate\_limit: null  
kube-controller:  
image: “”  
extra\_args: {}  
extra\_binds:   
extra\_env:   
win\_extra\_args: {}  
win\_extra\_binds:   
win\_extra\_env:   
cluster\_cidr: 10.42.0.0/16  
service\_cluster\_ip\_range: 10.43.0.0/16  
scheduler:  
image: “”  
extra\_args: {}  
extra\_binds:   
extra\_env:   
win\_extra\_args: {}  
win\_extra\_binds:   
win\_extra\_env:   
kubelet:  
image: “”  
extra\_args: {}  
extra\_binds:   
extra\_env:   
win\_extra\_args: {}  
win\_extra\_binds:   
win\_extra\_env:   
cluster\_domain: cluster.local  
infra\_container\_image: “”  
cluster\_dns\_server: 10.43.0.10  
fail\_swap\_on: false  
generate\_serving\_certificate: false  
kubeproxy:  
image: “”  
extra\_args: {}  
extra\_binds:   
extra\_env:   
win\_extra\_args: {}  
win\_extra\_binds:   
win\_extra\_env:   
network:  
plugin: canal  
options: {}  
mtu: 0  
node\_selector: {}  
update\_strategy: null  
tolerations:   
authentication:  
strategy: x509  
sans:   
webhook: null  
addons: “”  
addons\_include:   
system\_images:  
etcd: rancher/coreos-etcd:v3.4.15-rancher1  
alpine: rancher/rke-tools:v0.1.75  
nginx\_proxy: rancher/rke-tools:v0.1.75  
cert\_downloader: rancher/rke-tools:v0.1.75  
kubernetes\_services\_sidecar: rancher/rke-tools:v0.1.75  
kubedns: rancher/k8s-dns-kube-dns:1.15.2  
dnsmasq: rancher/k8s-dns-dnsmasq-nanny:1.15.2  
kubedns\_sidecar: rancher/k8s-dns-sidecar:1.15.2  
kubedns\_autoscaler: rancher/cluster-proportional-autoscaler:1.7.1  
coredns: rancher/coredns-coredns:1.6.9  
coredns\_autoscaler: rancher/cluster-proportional-autoscaler:1.7.1  
nodelocal: rancher/k8s-dns-node-cache:1.15.7  
kubernetes: rancher/hyperkube:v1.18.20-rancher1  
flannel: rancher/coreos-flannel:v0.12.0  
flannel\_cni: rancher/flannel-cni:v0.3.0-rancher6  
calico\_node: rancher/calico-node:v3.13.4  
calico\_cni: rancher/calico-cni:v3.13.4  
calico\_controllers: rancher/calico-kube-controllers:v3.13.4  
calico\_ctl: rancher/calico-ctl:v3.13.4  
calico\_flexvol: rancher/calico-pod2daemon-flexvol:v3.13.4  
canal\_node: rancher/calico-node:v3.13.4  
canal\_cni: rancher/calico-cni:v3.13.4  
canal\_flannel: rancher/coreos-flannel:v0.12.0  
canal\_flexvol: rancher/calico-pod2daemon-flexvol:v3.13.4  
weave\_node: weaveworks/weave-kube:2.6.4  
weave\_cni: weaveworks/weave-npc:2.6.4  
pod\_infra\_container: rancher/pause:3.1  
ingress: rancher/nginx-ingress-controller:nginx-0.35.0-rancher2  
ingress\_backend: rancher/nginx-ingress-controller-defaultbackend:1.5-rancher1  
metrics\_server: rancher/metrics-server:v0.3.6  
windows\_pod\_infra\_container: rancher/kubelet-pause:v0.1.6  
ssh\_key\_path: ~/.ssh/id\_rsa  
ssh\_cert\_path: “”  
ssh\_agent\_auth: false  
authorization:  
mode: rbac  
options: {}  
ignore\_docker\_version: null  
kubernetes\_version: “”  
private\_registries:   
ingress:  
provider: “”  
options: {}  
node\_selector: {}  
extra\_args: {}  
dns\_policy: “”  
extra\_envs:   
extra\_volumes:   
extra\_volume\_mounts:   
update\_strategy: null  
http\_port: 0  
https\_port: 0  
network\_mode: “”  
tolerations:   
cluster\_name: “”  
cloud\_provider:  
name: “”  
prefix\_path: “”  
win\_prefix\_path: “”  
addon\_job\_timeout: 0  
bastion\_host:  
address: “”  
port: “”  
user: “”  
ssh\_key: “”  
ssh\_key\_path: “”  
ssh\_cert: “”  
ssh\_cert\_path: “”  
monitoring:  
provider: “”  
options: {}  
node\_selector: {}  
update\_strategy: null  
replicas: null  
tolerations:   
restore:  
restore: false  
snapshot\_name: “”  
dns: null

---

<div class="post-metadata">

**Author:** ![superseb](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/superseb/32/2424_2.png) [@superseb](https://forums.suse.com/u/superseb)\
**Post date:** [August 30, 2021, 5:39pm UTC](https://forums.suse.com/t/unable-to-setup-kubernetes-cluster-using-rancher/21016/4 "2021-08-30T17:39:02Z")

</div>

Each node needs to have at least an address configured to reach over SSH, so the error is accurate in this case. Either use `rke config` or start with the minimal example [Rancher Docs: Example Cluster.ymls](https://rancher.com/docs/rke/latest/en/example-yamls/#minimal-cluster-yml-example)
