Evaluate support for backwards compatibility with TRLPolicy from Kuadrant

[jordigilh]

Question

Once #796 is merged, how are we going to keep Praxis being backwards compatible with Kuadrant's existing TRLPolicy? And the data (counters) persisted in Redis in prior versions by Limitador

Context

The proposed implementation for TRL in #796 breaks backwards compatibility with Kuadrant's TRLPolicy CRD. How can we reconcile both approaches so that our customers are not impacted?

Futhermore, users probably expect their existing counters to be forward compatible. If only through a clear upgrade path.

Approach

Understand on Kuadrant's approach and the changes from #796 and what are the differences. Design and propose changes to the praxis TRL that best address this gap.

Deliverables

• Design document detailing each of the evaluated approaches and the recommended one.
• Prototype in a dedicated branch

Timebox

No response

Area

Filter Pipeline

Parent Epic (optional)

#121

[jordigilh]

Related to #796

[jordigilh]

Related to Kuadrant/architecture#199

[alexsnaps]

Edited the description to reflect the scope of the feature aspect of this migration.
Beyond that, we also need to consider - once this is all cleared out and a clear path forward is identified - what needs to be done to make the work done in #796 robust for productions workloads.