I am looming to move to Kubernetes with longhorn as the storage back end. However, I am very confused on how to expose services. Right now I have two reverse proxies to route outside traffic to the appropriate services. I am looking to recreate this in Kubernetes.

What is the easiest way to do this? I am confused about how kubernetes does networking. Is there a easy way to make a service listen on a IP that can be resolved by a reverse proxy?

Edit:

K3s has a built in system

https://docs.k3s.io/networking/networking-services

https://www.virtualizationhowto.com/2022/05/traefik-ingress-example-yaml-and-setup-in-k3s/

2 points

In a cloud environment just use a Service or an Ingress.

In a data center or bare metal environment I would either use Traefik or install MetalLB to map service endpoints to known addresses.

permalink
report
reply
1 point
*
1 point

Have you ever used MetalML? It seems promising

permalink
report
parent
reply
2 points

I use Cilium and Metal LB (if that’s what you meant) for my job and it’s pretty useful imo

permalink
report
parent
reply
2 points

Are you familiar with Traefik in any way? It will really pay off if you do.

permalink
report
reply

Homelab

!homelab@selfhosted.forum

Create post

Rules

  • Be Civil.
  • Post about your homelab, discussion of your homelab, questions you may have, or general discussion about transition your skill from the homelab to the workplace.
  • No memes or potato images.
  • We love detailed homelab builds, especially network diagrams!
  • Report any posts that you feel should be brought to our attention.
  • Please no shitposting or blogspam.
  • No Referral Linking.
  • Keep piracy discussion off of this community

Community stats

  • 2

    Monthly active users

  • 78

    Posts

  • 59

    Comments