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

Add in the upgrading guide to 3scale 2.11 that httpsPort should be used instead of the env var APICAST_HTTPS_PORT

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 2.11.1 GA
    • Documentation
    • 3
    • False
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started

      When upgrading to 2.11 you can't use the environment variable and must use the field httpsPort in the APIManager CRD as explained in this KCS created. When updating the APIManager with the httpsPort: 8334 the Service is updated with a named port/target port httpsproxy automatically.
       
      Currently the documentation of reference is in the 3scale-operator GH repo.

              Unassigned Unassigned
              rhn-support-avilatus Anna Vila Tusell
              Lluis Cavalle Lluis Cavalle
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: