Feature Overview (aka. Goal Summary)  

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

Goals (aka. expected user outcomes)

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.

Requirements (aka. Acceptance Criteria):

• M1: Customer's can request through SUPPORTEX to have log-linking enabled for all of their HCP machinepools
• M2: Customers can self-service enable/disable log-linking on a per-machinepool basis through the OCM clients
   

OCP documentation: https://docs.google.com/document/d/1UbrwxHIIegNnUWG-FnHChjLw5YigzFvyOP3VRsQ-mM0/edit

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

Out of Scope

High-level list of items that are out of scope.  Initial completion during Refinement status.

Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  Initial completion during Refinement status.

Interoperability Considerations

Which other projects and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.