Bug 1337633

Summary: What to do if ElasticSearch uses up all of it's storage
Product: OpenShift Container Platform Reporter: Eric Jones <erjones>
Component: LoggingAssignee: Luke Meyer <lmeyer>
Status: CLOSED DUPLICATE QA Contact: chunchen <chunchen>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.1.0CC: aos-bugs, wsun
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-19 16:50:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eric Jones 2016-05-19 16:47:37 UTC 
Description of problem:
The Aggregate Container Logging feature does not specify a way to cleanup the storage that is necessary for the logs.

Additional info:
3.2 apparently has the curator pod, but what is the recommended method for cleaning up the storage in 3.1?