Best Practice for logging Kubernetes LoadBalancer IPs interactions

1/26/2021

I have setup a Kubernetes Cluster on DigitalOcean with a LoadBalancer that is running my web-site application. Now I am wondering about the best practice to capture IP client (the visitor of the website) and its interactions with the website.

I stumbled upon some literature of course, both from DigitalOcean, Get client source IP with Kubernetes Load Balancer service, and from the official Kubernetes' documentation, Logging.

If I am not mistaken, a 'good' solution would be to setup an nginx Ingress that forwards the client IP to the LoadBalancer (as suggested in the DigitalOcean forum), and to deploy a container engine inside the cluster that will fetch logs from the cluster and provisioning it to a third entity: a backend, ELK, etc...

Is this architecture a good one? Are there detailed tutorials regarding how to fetch IPs interactions within a LoadBalancer?

-- mazzespazze
digital-ocean
ip
kubernetes
load-balancing

0 Answers