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

Details

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

    Description

      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.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. THREESCALE-8040 Update the example to expose the service in TLS Client Certificate Validation to be consistent with the operator deployment

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          links to

          Web Link How to use https port in 3scale 2.11 deployed with the Operator

          Activity

            People

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

              Dates

                Created:
                Updated: