How to redirect the Apache log in Kubernetes

Question

I am having one namespace and one deployment(replica set), My Apache logs should be written outside the pod, how is it possible in Kubernetes.

question from:https://stackoverflow.com/questions/65599797/how-to-redirect-the-apache-log-in-kubernetes

Answer 1

This is a Community Wiki answer so feel free to edit it and add any additional details you consider important.

You should specify more precisely what you exactly mean by outside the pod, but as David Maze have already suggested in his comment, take a closer look at Logging Architecture section in the official kubernetes documentation.

Depending on what you mean by "outside the Pod", different solution may be the most optimal in your case.

As you can read there:

Kubernetes provides no native storage solution for log data, but you can integrate many existing logging solutions into your Kubernetes cluster ... Cluster-level logging architectures are described in assumption that a logging backend is present inside or outside of your cluster.

Here are mentioned 3 most popular cluster-level logging architectures:

• Use a node-level logging agent that runs on every node.
• Include a dedicated sidecar container for logging in an application pod.
• Push logs directly to a backend from within an application.

Second solution is widely used. Unlike the third one where the logs pushing needs to be handled by your application container, sidecar approach is application independend, which makes it much more flexible solution.

So that the matter was not so simple, it can be implemented in two different ways:

• Streaming sidecar container
• Sidecar container with a logging agent