Release Notes

Red Hat 3scale API Management 2.6

For Use with Red Hat 3scale API Management 2.6

Red Hat Customer Content Services

Abstract

Release Notes for Red Hat 3scale API Management 2.6.

Preface

This document is intended for use with Red Hat 3scale API Management and related patch releases.

Chapter 1. Red Hat 3scale API Management 2.6.1 - Patch release

This document is intended for use with Red Hat 3scale API Management 2.6.1 On-premises.

1.1. Resolved issues

Chapter 2. Red Hat 3scale API Management 2.6

This document is intended for use with Red Hat 3scale API Management 2.6 On-premises.

2.1. Supported configurations

  • Check the latest information about 3scale 2.6 supported configurations at the Red Hat 3scale API Management Supported Configurations website.
  • The operator image should only be installed using the supported Operator Lifecycle Manager (OLM) installation procedure. It is not intended to be installed manually.

2.2. New features

2.2.1. Major features

2.2.2. Minor features

2.3. Resolved issues

2.4. Documentation

2.5. Technology Preview features

2.6. Known issues

  • Pipeline examples from end-to-end solution for API lifecycle with 3scale toolbox are supported only on OCP 3.11 (Content from issues.jboss.org is not included.JIRA #2583).

  • When you change the OpenID Connect Authorization Flow in 3scale, Zync does not update the Red Hat Single Sign-On (RH-SSO) clients of 3scale applications (Content from issues.jboss.org is not included.JIRA #3025). To work around this issue, you have these alternatives:

    • For existing applications, update 3scale application such as a change in the description: This will trigger an update that will modify the RH-SSO client for the application.
    • Create a new application: This will create a new RH-SSO client with the correct authorization flows.

  • When importing or exporting application plan features and limits, modifying the exported YAML file is not supported (Content from issues.jboss.org is not included.JIRA #2350).

    • The sample pipelines and applications are provided as examples only. Any modifications that you make to the pipelines are not directly supported by Red Hat. The underlying APIs, CLIs, and interfaces leveraged by the sample pipelines are fully supported by Red Hat.
  • When using 3scale toolbox from an OpenShift image, you cannot add custom certificates (Content from issues.jboss.org is not included.JIRA #3102).

  • Makefile available to support customers migrating 3scale 2.5 to Redis Enterprise, and any other single-logical database Redis deployment.

  • Operator does not accept REDIS_STORAGE_SENTINEL_HOSTS and REDIS_QUEUES_SENTINEL_HOSTS in the backend-redis secret when configuring 3scale HA using Redis Sentinels (Content from issues.jboss.org is not included.JIRA #3258).

2.7. Changes in 3scale 2.6

2.7.1. Removed features

  • As OpenShift 4.x has removed wildcard routes, this feature is not available in 3scale 2.6. Instead, routes are created automatically with Zync. For more details about route creation, see the following documentation:

  • In 3scale 2.6, Oracle database with OpenShift 4.1 is not supported.
  • As announced in 3scale 2.5, compatibility with Microsoft Internet Explorer 11 (IE11) is not supported from 2.6.

2.7.2. Deprecated and removed features

  • Adyen payment gateway. In 3scale 2.6 it is removed but still supported for the existing configurations. For current installations where the accounts have their billing configured to use Adyen, it will keep visible and working. Users using another payment gateway will not be able to choose or see Adyen.

2.7.3. Future changes

  • The installation process is changing from template-based to operator-based. In this release we are introducing support for installing 3scale using the 3scale operator. In future releases we are planning on introducing support for upgrade-based operator and also for capabilities regarding service provisioning.

Legal Notice

Copyright © 2020 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at Content from creativecommons.org is not included.http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.