-
Feature
-
Resolution: Unresolved
-
Major
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
False
-
None
-
None
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
Feature Overview (aka. Goal Summary)
Support multiple HAProxy versions within an OpenShift release in order to enable rollbacks to a previous version or pretesting of features on a future version.
Goals (aka. expected user outcomes)
The goals are to have multiple HAProxy versions for an Openshift release, one previous version and one forward version.
Requirements (aka. Acceptance Criteria)
No issues or changes at 5.0
| Deployment considerations | List applicable specific needs (N/A = not applicable) |
| Self-managed, managed, or both | |
| Classic (standalone cluster) | |
| Hosted control planes | |
| Multi node, Compact (three node), or Single node (SNO), or all | |
| Connected / Restricted Network | |
| Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) | |
| Operator compatibility | |
| Backport needed (list applicable versions) | |
| UI need (e.g. OpenShift Console, dynamic plugin, OCM) | |
| Other (please specify) |
Use Cases (Optional):
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.
Questions to Answer (Optional):
Impact at upgrade time?
When HAProxy version is made (Day0 or Day2)?
Out of Scope
Background
Customer Considerations
Documentation Considerations
Interoperability Considerations
- relates to
-
NE-2215 Support multiple HAProxy versions in an OpenShift release
-
- In Progress
-