[Bug]: Unwanted empty Load Balancer is created even if not requested about terraform-hcloud-kube-hetzner HOT 4 CLOSED

I will do that as soon as I have time with a much simpler config file

from terraform-hcloud-kube-hetzner.

@roberto-sebastiano Look at the created_at time, that's not a bug. Maybe you inadvertently deployed something that created service of type LB. If you did that, the CCM would automatically create one for you!

You can use kubectl get svc -A to find out the name and kubectl delete it afterwards, unless it comes from a helm chart, in which case you should change the helm chart values file.

from terraform-hcloud-kube-hetzner.

@mysticaltech, I think it is a bug, because the created time is indeed an indication that 16 minutes ago book-test-nginx was created by terrafgorm

testing-nginx was created by me manually 5 hours ago

Also, this is the output of terraform plan from scratch, I report only the lb section given the kube.tf above

# module.kube-hetzner.hcloud_load_balancer.cluster[0] will be created
  + resource "hcloud_load_balancer" "cluster" {
      + delete_protection  = false
      + id                 = (known after apply)
      + ipv4               = (known after apply)
      + ipv6               = (known after apply)
      + labels             = {
          + "cluster"     = "book-test"
          + "engine"      = "k3s"
          + "provisioner" = "terraform"
        }
      + load_balancer_type = "lb11"
      + location           = "fsn1"
      + name               = "book-test-nginx"
      + network_id         = (known after apply)
      + network_ip         = (known after apply)
      + network_zone       = (known after apply)

      + algorithm {
          + type = "round_robin"
        }
    }

Can you reopen the bug please or give a solution ?
That's not good for automation

--
Roberto

from terraform-hcloud-kube-hetzner.

You have everything custom, from the IPs to the helm values, so there's not much we can do here, sorry. Please find the debug section in the readme and dive deep, if indeed you find that it's coming from us and not the custom values, then please reopen a new task with a kube.tf to reproduce that without custom values and I will definitely try to reproduce. Thanks for your understanding.

from terraform-hcloud-kube-hetzner.