Having an issue I think I setup k3s on Harvester via Rancher rancher-users #k3s

Title

salmon-afternoon-72196

01/02/2023, 7:45 PM

Having an issue, I think.... I setup k3s on Harvester via Rancher, everything works fine except it seems like my networking is backwards. On my load balancer I am getting multiple external ip's for each node that is accessible externally, the ips are from dhcp from my external router. What I am trying to do is have a external facing load balancer so that it can do routing based on prefix. I am also using Cloudlare. Any recommendations?

late-needle-80860

01/02/2023, 7:52 PM

Hi @salmon-afternoon-72196, That’s very little info on quite a complex challenge. Can you tell more. • Where’s your load-balancer running?

salmon-afternoon-72196

01/04/2023, 4:51 PM

I will do my best since I am relatively new to this

👍 1

late-needle-80860

01/04/2023, 4:51 PM

Wonderful thanks

salmon-afternoon-72196

01/04/2023, 4:51 PM

• Where’s your load-balancer running? ◦ inside the cluster ◦ or external to the cluster • What load-balancer are you using? • How are your running Harvester? ◦ on bare metal directly? ◦ or some other way?

I assumed since Harvester is acting like Cloud Provider that there might be some way to get a LoadBalancer or VIP from it.

spec: ingressClassName: traefik rules: - host: helloworld.apps.mikecarr.net http: paths: - backend: service: name: hello-world port: number: 80 path: / pathType: Prefix status: loadBalancer: ingress: - ip: 10.100.0.35 - ip: 10.100.0.36 - ip: 10.100.0.37

This is the Load balancer I was referring to

This works as long as I point CloudFlare to one of the ingress ip's. How can I get a single ip, vip or load balancer, to point to the ingress ip's?

I hope this makes sense 🙂

late-needle-80860

01/04/2023, 7:34 PM

Harvester is not really a cloud provider. It’s an HCI - a hyper-converged infrastructure platform.

The Traefik provided with K3s is an ingress-controller. An ingress-controller have specific concerns on a kubernetes controller. It’s a specific Kubernetes operator.

It is balancing & routing traffic. But, only HTTP/HTTPS traffic. Further, it provides a nice way of integrating with e.g. cert-manager for TLS termination

So as you don’t have a cloud provider on your hands you want to have an operator on the Kubernetes cluster you just installed to provide IP’s to your Traefik ingress-controller. And likely a static one.

Into the room comes metallb, kube-vip & purelb as the most known in that space. Go with metallb start_ing out._

salmon-afternoon-72196

01/09/2023, 12:08 AM

Thank you for the info, I have had covid this week so I have been resting and not working on this.

late-needle-80860

01/09/2023, 9:58 PM

Sure! good health to you. Get well soon and good luck with the issue - reply if you have more trouble

5 Views

#k3s Join Slack