getting issues while creating a simple cluster

[kunoSchlonz]

i simply created a testcluster with this script. i adjusted only a few things:

control_plane_nodepools = [
    {
      name        = "control-plane-nbg1",
      server_type = "cpx11",
      location    = "nbg1",
      labels      = [],
      taints      = [],
      count       = 1
    }
]
agent_nodepools = [
    {
      name        = "standard-4GB-agentpool",
      server_type = "cx21",
      location    = "nbg1",
      labels      = [],
      taints      = [],
      count       = 3
    }
]
  load_balancer_type     = "lb11"
  load_balancer_location = "nbg1"
  cluster_name = "wip-uat-cluster"

so roughly after 20mins i got the following error message

╷
│ Error: remote-exec provisioner error
│ 
│   with module.kube-hetzner.null_resource.kustomization,
│   on .terraform/modules/kube-hetzner/init.tf line 247, in resource "null_resource" "kustomization":
│  247:   provisioner "remote-exec" {

after restarting the script by terraform apply -auto-approve
it says

  # module.kube-hetzner.null_resource.kustomization is tainted, so must be replaced
-/+ resource "null_resource" "kustomization" {
      ~ id = "6255265822238195463" -> (known after apply)
    }

Plan: 3 to add, 0 to change, 1 to destroy.

then next it shows some issue withe the loadbalancer

module.kube-hetzner.null_resource.kustomization: Still creating... [3m10s elapsed]
module.kube-hetzner.null_resource.kustomization (remote-exec): Waiting for load-balancer to get an IP...
module.kube-hetzner.null_resource.kustomization (remote-exec): Waiting for load-balancer to get an IP...
module.kube-hetzner.null_resource.kustomization (remote-exec): Waiting for load-balancer to get an IP...
module.kube-hetzner.null_resource.kustomization (remote-exec): Waiting for load-balancer to get an IP...
╷
│ Error: remote-exec provisioner error
│ 
│   with module.kube-hetzner.null_resource.kustomization,
│   on .terraform/modules/kube-hetzner/init.tf line 247, in resource "null_resource" "kustomization":
│  247:   provisioner "remote-exec" {
│ 
│ error executing "/tmp/terraform_974140493.sh": Process exited with status 124

any ideas or suggestions?

[mysticaltech]

@kunoSchlonz Which platform are you using? If on Windows, you have to use WSL.

Also, please make sure to run terraform init -upgrade to fetch the latest.

Finally, if none of the above work, please do share your full kube.tf without hetzner token of course.

[kunoSchlonz]

im using a mac. and of course i did terraform init -upgrade
here is the config

locals {
  hcloud_token = "**"
}

module "kube-hetzner" {
  providers = {
    hcloud = hcloud
  }
  hcloud_token = local.hcloud_token
  source = "kube-hetzner/kube-hetzner/hcloud"
  ssh_public_key = file("~/.ssh/id_ed25519.pub")
  ssh_private_key = file("~/.ssh/id_ed25519")
  network_region = "eu-central" # change to `us-east` if location is ash
  control_plane_nodepools = [
    {
      name        = "control-plane-nbg1",
      server_type = "cpx11",
      location    = "nbg1",
      labels      = [],
      taints      = [],
      count       = 1
    }
  ]

  agent_nodepools = [
    {
      name        = "standard-4GB-agentpool",
      server_type = "cx21",
      location    = "nbg1",
      labels      = [],
      taints      = [],
      count       = 3
    }
  ]
  load_balancer_type     = "lb11"
  load_balancer_location = "fsn1"

provider "hcloud" {
  token = local.hcloud_token
}

terraform {
  required_version = ">= 1.3.3"
  required_providers {
    hcloud = {
      source  = "hetznercloud/hcloud"
      version = ">= 1.35.2"
    }
  }
}

output "kubeconfig" {
  value     = module.kube-hetzner.kubeconfig
  sensitive = true
}

[mysticaltech]

@kunoSchlonz You kube.tf seems ok. Did you try applying again?

The error means that the LB is not getting an IP from the CCM. Maybe the ingress controller is not deploying somehow.

Two things.

Post the output of kubectl get pods -A and kubectl get svc -A.

And, SSH into the node (see readme) and execute /tmp/terraform_974140493.sh again, and post the error message.