Kubernetes Sidecar Pattern: Shipping Nginx Logs Without Modifying the Main Container

The Kubernetes sidecar pattern allows developers to extend a main container's functionality by attaching a secondary container within the same pod. In this setup, an nginx container handles web serving while a separate Ubuntu-based sidecar container is responsible solely for reading and forwarding access and error logs. Both containers share an emptyDir volume mounted at /var/log/nginx, enabling the sidecar to periodically read logs every 30 seconds without altering nginx's configuration. This approach follows the separation of concerns principle, keeping each container focused on a single responsibility. The pattern is particularly useful when developers need recent log data, such as the last 24 hours, routed to a log-aggregation service without bloating the primary application container.