Epic Goal

Why is this important?

• MicroShift currently uses a hard coded audit log policy. It should be configurable to customer needs, like it is with OpenShift

Function Requirement Doc: 

• Detailed Functional Requirements: Google Doc

Acceptance Criteria

• Audit Config API: Microshift exposes audit configurability in parity to Openshift's profile-based implementation. 
• Audit Log Location Config: MicroShift users may specify a custom location to store the files, such that they may be written to a dedicated volume or device.
• Audit Log Size and Retention: Microshift users may specify audit log file max file size and retention policy (e.g. 10 files of 10G each) before they rotate
• User Documention: User documentation details the audit configuration API and default values, and provides examples covering common/expected scenarios. The different audit log policies and their description can be re-used from above quoted OpenShift docs.
• CI Coverage: CI test harness includes scenarios covering each configurable API and at least 1 expected holistic configuration.

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>