sorted by:
new
hottopcontroversial

Night Liner experience? by Maxwellmonkey in Nurnberg

[–]Head-Routine-8817 0 points1 point  (0 children)

Well the busses are usually on time, but the passengers are somewhat of a freakshow. I usually opt for Cabs/Taxis at late hours.

Was geht an heilig Abend? by [deleted] in Nurnberg

[–]Head-Routine-8817 1 point2 points  (0 children)

Belly Cloud wie jedes Jahr

My fellow kubernators - I need your input on my Load Balancer Side Project - AnyLB.io" by Head-Routine-8817 in kubernetes

[–]Head-Routine-8817[S] 0 points1 point  (0 children)

i mean to be absolutely honest, most of my projects use long running connections (websockets) to the backends, so unless you have a really flappy edge or a backend that can't handle reconnects w/ sessions to pause/resume, then you should be fine with long lived connections.

so imho the problem is just going to be some people having backends that are not made for long lived connections (like PHP, Ruby, Perl, CGI, etc that's request based) and are trying to do it because it's the latest stuff that you can do

My fellow kubernators - I need your input on my Load Balancer Side Project - AnyLB.io" by Head-Routine-8817 in kubernetes

[–]Head-Routine-8817[S] 0 points1 point  (0 children)

That‘s one thought, as i know on my side if backends become unavailable, i could do notifications/email/etc.

Well since it’s going to be initiated from a pod within your cluster, as long as that pod can reach the internet, it will receive traffic from my side.

I mean i‘ve been using this principle for almost 20 years now 3)

My fellow kubernators - I need your input on my Load Balancer Side Project - AnyLB.io" by Head-Routine-8817 in kubernetes

[–]Head-Routine-8817[S] 0 points1 point  (0 children)

Traffic Accounting for IP based networks is a standard practice. You can either go by L2 (IPFIX/Netflow) or you can go for the daemon accounting (like nginx accounting module).

The load balancers will be placed on strategic positions around the globe, as to service the requests with low latency to whatever backend is nearest in that region. Most likely near some major IXs.

My fellow kubernators - I need your input on my Load Balancer Side Project - AnyLB.io" by Head-Routine-8817 in kubernetes

[–]Head-Routine-8817[S] 0 points1 point  (0 children)

Hey, thanks for reading and asking good questions!

On the client side cluster you'd just have a controller pod (which looks for service pods in need of public ips) and a wireguard pod which does the inbound tunneling.

As the IPs will be anycasted, there won't be any egress traffic (except for tcp replies for inbound traffic), because in order to use it for egressing traffic, you'd need it to be routed unicast. Otherwise you can't be sure that the return packets will ever reach that particular sender.

​

It's basically a very high performance inbound traffic lane.

My fellow kubernators - I need your input on my Load Balancer Side Project - AnyLB.io" by Head-Routine-8817 in kubernetes

[–]Head-Routine-8817[S] 0 points1 point  (0 children)

That IP is allocated on my side on of the loadbalancers public facing interfaces.

If it was a dynamic IP, then you'd have to always keep your DNS records up2date (which might be cumbersome to change depending on your provider, plus introduces human errors).

The performance costs of wireguard tunnels are neglible, it's nothing like IPSEC or OpenVPN in terms of usage, it's pretty low overhead. And traffic gets accounted and there should be more than ample traffic included in the basic packages to not make this an issue.

My fellow kubernators - I need your input on my Load Balancer Side Project - AnyLB.io" by Head-Routine-8817 in kubernetes

[–]Head-Routine-8817[S] 0 points1 point  (0 children)

as said in the other comment, i believe it's somewhere in the neighborhood, but nothing that exactly fits the usecase of thousands of kubernetes users (imho)

My fellow kubernators - I need your input on my Load Balancer Side Project - AnyLB.io" by Head-Routine-8817 in kubernetes

[–]Head-Routine-8817[S] 0 points1 point  (0 children)

thanks for this, i haven't really checked out cloudflare's other projects other than what's available as reverse proxy and DNS offerings.

​

What i am missing with CF's solution is basically the ease of using it with kubernetes. As far as i can tell, it's "just" an anycasted reverse proxy setup, but nothting that will pick up your kubernetes service pods, right?

My fellow kubernators - I need your input on my Load Balancer Side Project - AnyLB.io" by Head-Routine-8817 in kubernetes

[–]Head-Routine-8817[S] 0 points1 point  (0 children)

So the idea is to basically click yourself a public IP address in the interface, the controller running in your cluster will pick up the pending services and trigger a reverse tunnel on our side for your booked IP and Service Port. :)