Epic Goal

Support multiple HAProxy versions within an OpenShift release in order to enable rollbacks or pretesting.

For example, OpenShift 4.22 should have an option for the version of HAProxy that was GA in OpenShift 4.21. Additionally, OpenShift 4.22 could have a newer version of HAProxy available as a TechPreviewNoUpgrade option.

Why is this important?

This epic enables the following use-cases:

• As a customer, I need to be able to configure OpenShift to use the next-to-last version of HAProxy, so that I can downgrade HAProxy if it causes problems after an upgrade.

• As a customer, I want to be able to try the next version of HAProxy, so that I can test new capabilities and report issues early.

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. RPM builds of multiple HAProxy versions.
2. ...

Previous Work (Optional)

1. …

Open questions

1. Should we allow specifying a specific HAProxy major version ("HAProxy2", "HAProxy3"), minor version ("HAProxy28", "HAProxy32"), stream (for example, "previous", "stable", "experimental"), or something else?
2. How will we handle removal or deprecation of an older HAProxy version from the list of allowed options?
3. Will we ship multiple container images, or one container image with multiple HAProxy executables? OpenSSL version is an important variable, which might push us towards shipping multiple images.
4. ...