Alejandro Colomar

> Hello Alex (@alejandro-colomar), > > Glad I was able to answer your question! > > > Would a solution that works for Linux only work for you? Which kernel...

I'm not saying we're not going to implement Unix sockets. We are. And I'm about to commit the changes into the master branch (I wanted to clear up a few...

I didn't solve the problem with Unix domain filesystem sockets because: - Unix domain abstract sockets don't have that problem, so you can switch to using them, and the problem...

> How can you implement this exchange (communication between two applications) through an abstract socket? Please explain this to me? Exactly as you would with unix sockets. See an example...

> But in the previous sentence you refer to, I gave a specific example that involves interacting with a socket from two independent containers. > > > I'm talking about...

> > As far as I know, pods in the same node share the network namespace, but I'm not sure about that > > Hello Alex, > > I apologize...

> > But if you put the **two containers in the same pod** [...] they'll be able to communicate that way between them. > > Would you be able to...

I'm referring to this: https://www.mirantis.com/blog/multi-container-pods-and-container-communication-in-kubernetes/ which you'll notice that mentions as a use case having nginx as a reverse proxy before the actual app (unit in this case).

With my srv_a and cli_a programs, the YAML would look something like the following: ```yaml apiVersion: v1 kind: Pod metadata: name: server_and_client spec: containers: - name: server image: srv_a command:...

> > I'm referring to this: > > https://www.mirantis.com/blog/multi-container-pods-and-container-communication-in-kubernetes/ > > which you'll notice that mentions as a use case having nginx as a reverse proxy before the actual app...