There are various reasons data gaps could occur

• Configuration may be incorrect
• Network issues or proxies without proper configuration
• Uninstalling the operator and reinstalling (perhaps days later)
• Operator bug

The goal is for the operator to add some resiliency to allow the customer to recovery from these gaps.

Criteria:
1. Operator should check for retention policy in the `cluster-monitoring-config` ConfigMap in `openshift-monitoring`. The default is 15d. The operator should gather no more than this default or specified value in the retention-policy and override the days specified by the customer.
2. Operator should retry a failed query x times before moving on to a new time range. Queries should start at the `last_query_success_time`, retry until failure, and move to the next hour.

Target Dates

• Operator development work complete - June 23, 2023
• QE testing complete- June 30, 2023