-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
openshift-4.13
-
Add an IngressController option to use PROXY protocol with AWS Cloud load-balancers
-
BU Product Work
-
False
-
None
-
False
-
Green
-
To Do
-
OCPSTRAT-356 - Add an IngressController Option to Use PROXY Protocol with AWS Cloud Load-Balancers
-
OCPSTRAT-356Add an IngressController Option to Use PROXY Protocol with AWS Cloud Load-Balancers
-
100% To Do, 0% In Progress, 0% Done
-
0
-
0
This epic tracks the API and implementation work to provide the cluster admin with an option in the IngressController API to use PROXY protocol with AWS Cloud load-balancers.
This epic extends the IngressController API essentially by copying the option we added in NE-330. In that epic, we added a configuration option to use PROXY protocol when configuring an IngresssController to use a NodePort service or host networking. With this epic (NE-1090), the same configuration option is added to use PROXY protocol when configuring an IngressController to use a LoadBalancer service on AWS Cloud.
Customers seek the ability to pass proxyProtocol v2 to AWS load balancers (as in demand by several ROSA/OSD customers)
- clones
-
NE-1090 Add an IngressController option to use PROXY protocol with IBM Cloud load-balancers
- Closed
- incorporates
-
OCPSTRAT-356 Add an IngressController Option to Use PROXY Protocol with AWS Cloud Load-Balancers
- New