What is the business rationale for this exception? Is there a specific customer that needs this RFE?

Answer: This has been mentioned in passing as a 'nice to have' by a number of customers.  Since  nearly all the effort  is complete and the code has been in the codebase for some time this is a minimal risk feature to include without adding to the QE burden of verification for OSP 18/OSO 1.  The idea would be to target this to 17.1.3.

Are there any security concerns?

Answer: no.

What other functions, teams, or DFGs are impacted by this feature?

Answer: QE effort is almost complete; the only other impact is some small docs work.

What is the estimated time to have the upstream work complete and approved?

Answer: Upstream dev work is complete except for a tempest test that is close to being merged; QE manual verification is estimated to be complete by end of week.

What is the time and resources required to test this issue? On what date will automated tests be written and ready to run and report results in Polarion?

Answer: Automated tests are written and about to be merged, verification estimated to be done by end of week.

Is there potential doc impact?

Answer: Yes, importing the upstream docs will be 90% of the doc work but some polishing will be needed.

Are there new packages needed that are not packaged in OSP or RHEL? Does it require newer versions of existing dependencies (dependency bumps)?

Answer: no

What is the support level? Tech Preview or fully supported

Answer: This is for full support

How invasive is the code? From very invasive, a core change to very isolated, no risk to other components?

Answer: The code has been in Octavia for some time, this is just the final QE verification of the feature.  No risk to other components.

What is the impact to deployment/updates/upgrades/FFU; what are the test plans in these areas?

Answer: No impact.