search

equinix-labs / terraform-equinix-kubernetes-cluster

Kubernetes cluster deployment on Equinix Metal
https://registry.terraform.io/modules/equinix-labs/kubernetes-cluster/equinix/latest
Apache License 2.0
1 stars 5 forks source link

Elastic IP not being assigned to nodes #44

Closed austinlparker closed 9 months ago

austinlparker commented 9 months ago

When trying to run the module, I'm getting the following error --

module.terraform-equinix-k8s-cluster.null_resource.kubeconfig: Provisioning with 'local-exec'...
module.terraform-equinix-k8s-cluster.null_resource.kubeconfig (local-exec): Executing: ["/bin/sh" "-c" "scp -o StrictHostKeyChecking=no -i ssh_key root@145.40.80.244:/etc/kubernetes/admin.conf kubeconfig.admin.yaml"]
module.terraform-equinix-k8s-cluster.null_resource.kubeconfig: Still creating... [10s elapsed]
module.terraform-equinix-k8s-cluster.null_resource.kubeconfig: Still creating... [20s elapsed]
module.terraform-equinix-k8s-cluster.null_resource.kubeconfig: Still creating... [30s elapsed]
module.terraform-equinix-k8s-cluster.null_resource.kubeconfig: Still creating... [40s elapsed]
module.terraform-equinix-k8s-cluster.null_resource.kubeconfig: Still creating... [50s elapsed]
module.terraform-equinix-k8s-cluster.null_resource.kubeconfig: Still creating... [1m0s elapsed]
module.terraform-equinix-k8s-cluster.null_resource.kubeconfig: Still creating... [1m10s elapsed]
module.terraform-equinix-k8s-cluster.null_resource.kubeconfig (local-exec): ssh: connect to host 145.40.80.244 port 22: Operation timed out
module.terraform-equinix-k8s-cluster.null_resource.kubeconfig (local-exec): scp: Connection closed
╷
│ Error: local-exec provisioner error
│
│   with module.terraform-equinix-k8s-cluster.null_resource.kubeconfig,
│   on .terraform/modules/terraform-equinix-k8s-cluster/main.tf line 119, in resource "null_resource" "kubeconfig":
│  119:   provisioner "local-exec" {
│
│ Error running command 'scp -o StrictHostKeyChecking=no -i ssh_key root@145.40.80.244:/etc/kubernetes/admin.conf kubeconfig.admin.yaml': exit status 255. Output: ssh: connect to host 145.40.80.244 port 22: Operation
│ timed out
│ scp: Connection closed

It seems like the EIP isn't being associated with the control plane nodes, even though it's being created.

austinlparker commented 9 months ago

I'm looking at cloud-init logs and I'm wondering if this is because the node bootstrapping is failing?

austinlparker commented 9 months ago

yep, this was failing because the k8s version wasn't available so cloud-init failed.