Closed roberto-sebastiano closed 7 months ago
@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.
@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
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.
I will do that as soon as I have time with a much simpler config file
Description
I'm trying to avoid this project create any load balancers for the testing environment. The only load balancer that I want to persist during destroy / apply terraform cycles is called
testing-nginx
that I created manually. (see screenshot below)This manually created load balancer is working correctly (nginx registers the nodes and it works for the ingress), but an unwanted one gets created with 0 servers registered during terraform apply, named
book-test-nginx
I'm unable to find any reference of it in
kube.tf
. This setup is a simple 1 control plane + 2 worker nodes, so no control plane load balancer is needed, and as I said the ingress lb is created manuallyIs this a bug ? How to avoid creating any load balancers in this project ?
Thanks, Roberto Sebastiano
Kube.tf file
Screenshots
Platform
Mac