Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-6306

Make configurable the OCP route timeout values for routes that are generated by Zync.

XMLWordPrintable

    • False
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • 0
    • 0% 0%
    • 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?
       

            Unassigned Unassigned
            rhn-support-tkonishi Takayuki Konishi
            Votes:
            6 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: