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

OpenShift routes are created without TLS configuration

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 2.9 GA
    • None
    • Zync
    • None
    • Invalid Sprint

      zync generated OpenShift routes do not have TLS configuration. It has been removed and system services are not accesible via HTTP or HTTPS when 3scale has just been installed (by 3scale operator).

      Route spec on 2.8:

      spec:
  host: 3scale-admin.eguzki-test.apps.dev-eng-ocp4-3.dev.3sca.net
  port:
    targetPort: http
  tls:
    insecureEdgeTerminationPolicy: Redirect
    termination: edge
  to:
    kind: Service
    name: system-provider
    weight: 100
  wildcardPolicy: None

      Route spec on "nightly" zync:

      spec:
  host: 3scale-admin.eguzki-test.apps.dev-eng-ocp4-3.dev.3sca.net
  port:
    targetPort: http
  to:
    kind: Service
    name: system-provider
    weight: 100
  wildcardPolicy: None

      Tested with "nightly" image:

      quay.io/3scale/zync@sha256:a43b7a513d473540edb82bcb558b5f2ea4045cabfa1974add025afe624292edf

      OCP 4.3

      See this comment

              Unassigned Unassigned
              eguzki Eguzki Astiz Lezaun
              Guilherme Cassolato Guilherme Cassolato
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: