Replies: 8 comments 15 replies
-
Hi, I just tested twice and I wasn't able to reproduce your issue. Each time I deleted the cluster, the targets were removed from the load balancer as soon as the servers were deleted as expected. When I recreated the cluster and reinstalled ingress-nginx, the existing load balancer was reused just fine and the new targets were added. Seems to work correctly for me. Perhaps you could raise this on the Hetzner Cloud Controller Manager project . |
Beta Was this translation helpful? Give feedback.
-
It should work like a charm. I use it very often, because I lock my LBs to not loose the public IP (like you). controller:
config:
use-proxy-protocol: "true"
service:
type: LoadBalancer
annotations:
load-balancer.hetzner.cloud/name: my-name
load-balancer.hetzner.cloud/location: fsn1
load-balancer.hetzner.cloud/use-private-ip: true
load-balancer.hetzner.cloud/algorithm-type: least_connections
load-balancer.hetzner.cloud/uses-proxyprotocol: true
load-balancer.hetzner.cloud/hostname: my-hostname But I don't think this will make any difference. Just checked my hcloud-controller-manager version. I use 1.16.0. |
Beta Was this translation helpful? Give feedback.
-
I'll convert this to a discussion since it doesn't seem to be a problem with hetzner-k3s. Thanks @derlinuxer for confirming it works for you too :) |
Beta Was this translation helpful? Give feedback.
-
Okay, many thanks for the replies. I opened a support ticket (#2023100903011459) at Hetzner including a screen recording showing exactly what's happening, so they hopefully can find out what's wrong. @derlinuxer Just to understand this better: Have you effectively tested the configuration shown here or are you just referring to your experience with your configurations? |
Beta Was this translation helpful? Give feedback.
-
FYI, Hetzner just responded that they assume a bug on their side and they are investigating it. |
Beta Was this translation helpful? Give feedback.
-
Hetzner informed me today that they deployed fixes that should resolve the problem. Indeed, I can no longer reproduce the issue 🎉 Very nice :-) |
Beta Was this translation helpful? Give feedback.
-
@jampy FYI I replied to your email yesterday but it seems like there is a problem with your mail server because of timeouts :) |
Beta Was this translation helpful? Give feedback.
-
can anyone help with testing rc1 of v2.0.0? see #385 for details |
Beta Was this translation helpful? Give feedback.
-
I've noticed a problem of hetzner-k3s in combination with ingress-nginx. I'm not sure wether this is a problem of hetzner-k3s or the
hetznercloud/csi-driver, so I'm posting it here.
Basically the problem is as follows:
hetzner-k3s create
, without any resources pre-existinghetzner-k3s delete
(the ingress load balancer is not deleted)This obviously means that recreating a cluster will leave it in a bad shape. I also wonder what will happen when nodes are added/replaced during the lifetime of a cluster since the targets configuration apparently is not very stable.
Detailed description to reproduce
I'm using
hcloud-k3s
Version 1.1.4 (even if--version
reports 1.1.3, but that's expected).My
cluster_config.yaml
:My
ingress-nginx-annotations.yaml
:I create the cluster using
hetzner-k3s create --config cluster_config.yaml
and that works fine, a total of 7 servers is started and thelb-targets-test-cluster-api
load balancer is started/configured and is healthy.Then I configure the Ingress and it's Load Balancer:
This creates the
lb-being-tested
load balancer, which after a while becomes healthy.Then I destroy the cluster using
hetzner-k3s delete --config cluster_config.yaml
. All servers are being destroyed, the API load balancer is deleted but thelb-being-tested
load balancer remains (as expected).Then I re-create the cluster using
hetzner-k3s create --config cluster_config.yaml
again, which brings up (different) Hetzner servers, of course. The API load balancer is recreated and becomes healthy again.Then I install ingress-nginx using Helm, just like before.
I would expect that the existing Load Balancer (and, most importantly, it's public IP address) is reused. However, no targets are configured on the load balancer, thus it doesn't become healthy. So, no ingress.
Side note: weird LB behavior after deleting the cluster
When deleting the cluster using
hetzner-k3s
without manually removing targets from the load balancer, thelb-being-tested
load balancer configuration is left as-is (as it is not managed by hetzner-k3s). Targets disappear very slowly (supposedly garbage collected by Hetzner itself) but the Hetzner UI shows inconsistent information about the targets, see here:Here it says "4 servers" but also "no targets".
Workaround
The problem is avoided by manually removing all targets from the load balancer, before deleting the cluster.
Note that even if targets are not manually removed, the load balancer will eventually show "no targets" automatically after deleting the cluster. This takes a few minutes(!). However, the load balancer is still not reconfigured properly after re-creating the cluster.
Detailed commands, logs
See here: https://pastebin.com/raw/XLe85iNr
Beta Was this translation helpful? Give feedback.
All reactions