Hardening access to the service running on the Container

I’m looking to tighten the access policy for a service running on a Container. Only 1 IP access to that service is allowed.
For example: I only want 1 IP to access the Kibana Service I built and expose as 5603:5601

Use a firewall on host, use a reverse-proxy like Traefik or implement the IP checking in the application.

1 Like