Question on SSL traffic between podman containers and clients (should I run k3s?)

MigratingtoLemmy@lemmy.world to Selfhosted@lemmy.world – 4 points –

Hi everyone.

I was trying to research about how to implement SSL on the traffic between my clients and the containers that I host on my server.

Basically, my plan was to use upstream SSL in HAProxy to attempt to achieve this, but in order for that to work, each individual container on my server needs to be able to decrypt SSL. I do not think that is possible and that every container has the necessary libraries for it. This puts a halt on my idea for upstream encryption of traffic from my reverse-proxy to my containers.

With that said, ChatGPT suggested I use Kubernetes with a service mesh like Istio. The idea was intriguing so I started to read about it; but before I dive head-first into using k3s (TBH it's overkill for my setup), is there any way to implement server-side encryption with podman containers and a reverse-proxy?

After writing all of this, I think I'm missing the point about a reverse-proxy being an SSL termination endpoint, but if my question makes sense to you, please let me know your thoughts!

Thanks!

25

You are viewing a single comment
View all comments

Why not just run a reverse proxy container on the server hosting the rest?

That's what I'm doing, but I would have liked encrypted communications between the other containers and the proxy too

But why?

I do not prefer to not have much, if any unencrypted traffic on my network

The traffic between containers should not be done over your normal network, you should set up a private network between containers. That way it won't matter if it's not encrypted.