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!

  • @vegetaaaaaaa
    link
    English
    1
    edit-2
    7 months ago

    No, they can’t, that’s the point of namespaces.

    • @MigratingtoLemmyOP
      link
      English
      17 months ago

      Even if containers from different pods are put in an arbitrary namespace?

      Ex:

      • pod 1 - network: pod1
      • pod 2 - network: pod2
      • Container1 and Container2 are spun up within these pods respectively, whilst also being attached to network: pod3

      Will they be able to connect via loopback?