Giters

hobby-kube / guide

Kubernetes clusters for the hobbyist.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Waiting for API server to respond (Digital Ocean)

damianesteban opened this issue · comments

commented

I could have sworn that I was able to provision a cluster a few weeks ago using these terraform modules but I'm now receiving the following error, and it just continues to print out Waiting for API server to respond...

module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[0] (remote-exec): [init] using Kubernetes version: v1.11.2
module.kubernetes.null_resource.kubernetes[0] (remote-exec): [preflight] running pre-flight checks
module.kubernetes.null_resource.kubernetes[0] (remote-exec): 	[WARNING Swap]: running with swap on is not supported. Please disable swap
module.kubernetes.null_resource.kubernetes[0] (remote-exec): I0814 00:10:05.192904   14243 kernel_validator.go:81] Validating kernel version
module.kubernetes.null_resource.kubernetes[0] (remote-exec): I0814 00:10:05.193231   14243 kernel_validator.go:96] Validating kernel config
module.kubernetes.null_resource.kubernetes.2: Still creating... (50s elapsed)
module.kubernetes.null_resource.kubernetes.1: Still creating... (50s elapsed)
module.kubernetes.null_resource.kubernetes.0: Still creating... (50s elapsed)
module.kubernetes.null_resource.kubernetes[0] (remote-exec): [preflight] Some fatal errors occurred:
module.kubernetes.null_resource.kubernetes[0] (remote-exec): 	[ERROR ExternalEtcdVersion]: this version of kubeadm only supports external etcd version >= 3.2.17. Current version: 3.2.13
module.kubernetes.null_resource.kubernetes[0] (remote-exec): 	[ERROR ExternalEtcdVersion]: this version of kubeadm only supports external etcd version >= 3.2.17. Current version: 3.2.13
module.kubernetes.null_resource.kubernetes[0] (remote-exec): 	[ERROR ExternalEtcdVersion]: this version of kubeadm only supports external etcd version >= 3.2.17. Current version: 3.2.13
module.kubernetes.null_resource.kubernetes[0] (remote-exec): [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes.2: Still creating... (1m0s elapsed)
module.kubernetes.null_resource.kubernetes.1: Still creating... (1m0s elapsed)
module.kubernetes.null_resource.kubernetes.0: Still creating... (1m0s elapsed)
commented

Try with the latest version, just merged a pull request related do this.

commented

Unfortunately no, still not working. It gets further along in the process but ends up here:

module.kubernetes.null_resource.kubernetes[2]: Provisioning with 'remote-exec'...
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Connecting to remote host via SSH...
module.kubernetes.null_resource.kubernetes[2] (remote-exec):   Host: 139.59.159.48
module.kubernetes.null_resource.kubernetes[2] (remote-exec):   User: root
module.kubernetes.null_resource.kubernetes[2] (remote-exec):   Password: false
module.kubernetes.null_resource.kubernetes[2] (remote-exec):   Private key: false
module.kubernetes.null_resource.kubernetes[2] (remote-exec):   SSH Agent: true
module.kubernetes.null_resource.kubernetes[2] (remote-exec):   Checking Host Key: false
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Connected!
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes.1: Still creating... (2m40s elapsed)
module.kubernetes.null_resource.kubernetes.0: Still creating... (2m40s elapsed)
module.kubernetes.null_resource.kubernetes.2: Still creating... (2m40s elapsed)
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes.2: Still creating... (2m50s elapsed)
module.kubernetes.null_resource.kubernetes.0: Still creating... (2m50s elapsed)
module.kubernetes.null_resource.kubernetes.1: Still creating... (2m50s elapsed)
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes.1: Still creating... (3m0s elapsed)
module.kubernetes.null_resource.kubernetes.0: Still creating... (3m0s elapsed)
module.kubernetes.null_resource.kubernetes.2: Still creating... (3m0s elapsed)
commented

Make sure to fetch the latest version of https://github.com/hobby-kube/provisioning and upgrade Terraform to 0.11.8.