Epic Goal

Ship HAProxy 3.2 in OpenShift router

Why is this important?

We need to ship HAProxy 3.2 in order to have a recent version of HAProxy that is still supported upstream.

The HAProxy website, <https://www.haproxy.org/>, lists the currently supported HAProxy versions and the end-of-life date for each of these versions. HAProxy 3.2 has an end-of-life date of 2030-Q2. HAProxy 2.8, which is included in OpenShift 4.16 through 4.21, has an end-of-life date of 2028-Q2.

Planning Done Checklist

The following items must be completed on the Epic prior to moving the Epic from Planning to the ToDo status

• Priority is set by engineering
• Epic must be Linked to a Parent Feature
• Target version must be set
• Assignee must be set
• Enhancement Proposal is Implementable
• No outstanding questions about major work breakdown
• Are all Stakeholders known? Have they all been notified about this item?
• Does this epic affect SD? Have they been notified? (View plan definition for current suggested assignee)
  1. Please use the “Discussion Needed: Service Delivery Architecture Overview” checkbox to facilitate the conversation with SD Architects. The SD architecture team monitors this checkbox which should then spur the conversation between SD and epic stakeholders. Once the conversation has occurred, uncheck the “Discussion Needed: Service Delivery Architecture Overview” checkbox and record the outcome of the discussion in the epic description here.
  2. The guidance here is that unless it is very clear that your epic doesn’t have any managed services impact, default to use the Discussion Needed checkbox to facilitate that conversation.

Dependencies (internal and external)

1. ...

Previous Work (Optional)

1. …

Open questions

1. …