Provisioning EKS-A in AT fails

equinix-labs / terraform-equinix-metal-eks-anywhere

EKS Anywhere on Equinix Metal (Baremetal)

https://deploy.equinix.com/labs/terraform-equinix-metal-eks-anywhere/

Apache License 2.0

9 stars 5 forks source link

Provisioning EKS-A in AT fails #92

Open 5herlocked opened 1 year ago

5herlocked commented 1 year ago

Bottlerocket does not seem to able to communicate with the EKS-A Admin node OR the tink-provisioner to pull userdata.

This is consistently happening when deploying m3 type machines in the AT region; but does not happen when using the same machines in the SV region.

Attached screenshots show fail state:

displague commented 1 year ago

@5herlocked it is possible that the name of the NIC device is different between the two nodes that you are deploying. The logs should show the kernel device name. This could be compared to the name defined in the Terraform variables and the NIC device that appears in the AT log.