Goal

• Support making containers logs in a pod available inside an emptyDir so they could be read/forwarded by a logging sidecar.

Why is this important?

• Customers want to be able to access container logs easily inside the pods so they could read them and log them to their sinks using logging side car containers. 

Scenarios

1. As an OpenShift cluster admin, I want my user to be able to forward logs using a logging side care without having to modify their application entrypoint.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>