Homelab

371 readers

9 users here now

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

founded 1 year ago

MODERATORS

communick@selfhosted.forum

rglullis@communick.news

Thoughts on Kubernetes networking (lemmy.zip)

submitted 3 months ago* (last edited 3 months ago) by possiblylinux127@lemmy.zip to c/homelab@selfhosted.forum

5 comments fedilink hide all child comments

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/

you are viewing a single comment's thread
view the rest of the comments

[–] lorgo_numputz@beehaw.org 2 points 3 months ago

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.