-
Task
-
Resolution: Done
-
Normal
-
None
-
3
-
False
-
False
-
NEW
-
OBSDA-123 - cluster logging - delete ES logs by PVC usage threshold
-
VERIFIED
-
Undefined
-
-
Logging (LogExp) - Sprint 210, Logging (LogExp) - Sprint 206, Logging (LogExp) - Sprint 207, Logging (LogExp) - Sprint 208, Logging (LogExp) - Sprint 209, Logging (LogExp) - Sprint 211
As a follow up from https://issues.redhat.com/browse/LOG-1326, we want to implement delete by query as part of index management script.
Acceptance Criteria:
- Ensure that the API changes are not breaking the current flow.
- Ensure that the user is able to specify the namespaces and minAge for performing delete by query.
- Ensure that the index management script is able to perform delete by query correctly.
- Ensure that CLO is able to consume the API changes for delete by query.
- Write possible test cases to check that delete by query is working correctly.
Dev Notes:
- The API changes and implementation details are here - https://docs.google.com/document/d/1JjdbspwYe-aYMBH65ybc9xBroOzoobPqrxwzFg9ZRGc/edit?usp=sharing
- account is impacted by
-
LOG-1757 Implemnet merge indices as part of Index Management
- Closed
- causes
-
LOG-2210 Delete by query doesn't delete all the projects' logs defined in retentionPolicy
- Closed
-
LOG-2216 Delete by query doesn't delete all the projects' logs defined in retentionPolicy
- Closed
-
LOG-2120 EO becomes CrashLoopBackOff when deploy ES with more than 3 nodes
- Closed
- is related to
-
OBSDA-324 Data cleanup and retention for logging
- Closed
- links to
(1 links to)