Description of problem

Users of ClusterLogForwarding with legacy vector deployments likely will experience a brief period of logs being ingested a second time. This is because the location of the legacy checkpoint system is different then mCLF or Logging 6.0. Depending upon the size of the OCP cluster and the number of workloads, this could result in a sizeable amount of storage.

Version-Release number of selected component (if applicable):

How reproducible:

Deploy logging 5.9 along with a legacy log collector.
Deploy logging 6.0 and convert the legacy CL/CLF combo to CLF.observability
Query logstore for duplicate log entries

Steps to Reproduce:

3. ...

Actual results:

Expected results:

Additional info: