-
Feature Request
-
Resolution: Won't Do
-
Minor
-
None
-
2.9.1 GA
-
False
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Undefined
-
On 3scale 2.5 or previous versions, users can configure OpenShift Route resources when the timeout value should be greater than 30s.
example:
metadata: annotations: haproxy.router.openshift.io/timeout: 120s
On 3scale 2.6 or later versions, even if users configure that, Zync overwrites that when it updates routes.
Make configurable the route timeout values.
Dev Notes
Check for any upper limit that we may have. If we have one, why did we add it and should it override configured limits that are too high?
- relates to
-
THREESCALE-3898 Clarify how to configure OCP route timetout along with Upstream Connection policy
- Closed
-
THREESCALE-8102 Make route creation in zync optional.
- To Test (QE)
- links to