Possibility to use systemd activated sockets with podman kube

[oryjkov]

What I want:

Run a kube deployment with several containers without access to outside world. Only allow access from outside via a few endpoints using systemd socket activation.

What I tried:

Created a systemd .kube file, systemd .socket file and the corresponding yaml kubernetes config. The .kube file depends on a systemd socket.

Result:

Containers do not inherit the systemd socket. Seems that only the -services container inherits the socket, but that makes it useless.,

I can run this setup using a systemd pod, but I found this configuration to be less ergonomic. It needs a bunch of separate files to describe the setup and it is not possible to generate it from an existing set of containers as podman kube generate does.

Question:

Is there a way to make this work with a kube?

more info in eriksjolund/podman-traefik-socket-activation#3