Release Notes for Red Hat 3scale API Management 2.13 On-premises
Document intended for use with Red Hat 3scale API Management 2.13
Abstract
Preface
This document is intended for use with Red Hat 3scale API Management 2.13 and related patch releases.
Chapter 1. Red Hat 3scale API Management 2.13.3 - Patch release
This document is intended for use with Red Hat 3scale API Management 2.13.3 On-premises.
1.1. New features
Red Hat 3scale API Management 2.13.3 provides the following new features:
- Red Hat 3scale API Management is now compatible with Red Hat OpenShift Container Platform 4.13 (THREESCALE-9586).
Chapter 2. Red Hat 3scale API Management 2.13.2 - Patch release
This document is intended for use with Red Hat 3scale API Management 2.13.2 On-premises.
2.1. Security updates
- Check the latest information about 3scale 2.13.2 security updates in the Red Hat Product Advisories portal.
Chapter 3. Red Hat 3scale API Management 2.13.1 - Patch release
This document is intended for use with Red Hat 3scale API Management 2.13.1 On-premises.
3.1. Resolved issues
Red Hat 3scale API Management 2.13.1 resolves the following issues:
Table 3.1. Resolved issues
| Issue number | Description |
|---|---|
| Upgrade with APIcast Operator from 2.12 to 2.13 fails |
Chapter 4. Red Hat 3scale API Management 2.13
This document is intended for use with Red Hat 3scale API Management 2.13 On-premises.
4.1. New features
Red Hat 3scale API Management 2.13 provides the following new features:
- Red Hat 3scale API Management deployed on OpenShift with FIPS (Federal Information Processing Standards) mode enabled is now supported (THREESCALE-5725).
- Minor user interface improvements (THREESCALE-825, THREESCALE-8270).
4.2. Technology Preview features
Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview/.
Red Hat 3scale API Management 2.13 provides the 3scale operator for application capabilities as a Technology Preview feature. The 3scale operator enables the use of custom resources to define 3scale tenants, APIs, application plans, limits, metrics, and other objects for use in a 3scale installation (THREESCALE-3486). See Using the 3scale operator to configure and provision 3scale.
3scale operator application capabilities have been improved in 3scale 2.13 with:
-
Ability to promote
Productconfigurations to Staging and Production APIcast (THREESCALE-7135) -
Declarative deletion of
DeveloperUser(THREESCALE-7055) andDeveloperAccount(THREESCALE-7052) custom resources.
4.3. Resolved issues
Red Hat 3scale API Management 2.13 resolves the following issues:
Table 4.1. Resolved issues
| Issue number | Description |
|---|---|
| Algorithm parameter JWK "alg" check should be optional. | |
| APIcast cannot retrieve latest version of proxy config | |
| APIcast strips request path for proxied https requests | |
| Autocomplete attribute for the credentials fields in the login page fixed | |
| Default plan card disappears when searching for plans. | |
| Too large request URIs make identifying errors in the APIcast logs difficult. | |
|
Nginx Filter policy UI - The boolean field is not | |
| The mapping rule search pagination is not displayed on the search results page. | |
| Searches incorrectly return all records when searching by the name of the class. |
4.4. Known issues
Known issues in Red Hat 3scale API Management 2.13:
Table 4.2. Known issues
| Issue number | Description |
|---|---|
| In 3scale, search does not work for products, backends, or accounts that are older than 24 hours | |
|
The NGINX Filters policy has no effect if you also add the Content Caching policy. The default behavior is that content caching is disabled. If you enable content caching, NGINX returns a | |
| Upgrade with APIcast Operator from 2.12 to 2.13 fails. For more information, refer to the workaround described in this knowledge article. Issue resolved in 2.13.1 |
Usernames in 3scale must be 40 characters or fewer. When a username has more than 40 characters, 3scale usually truncates it. Consider this when you do any of the following:
- Create a developer account.
- Create a provider account as the master.
- Add a user to a provider account as the provider or as the master.
- Add a user to a developer account in the Developer Portal or in the Admin Portal.
- Usernames must be 40 characters or fewer when using Red Hat Single Sign-On to authenticate access to the Admin Portal or Developer Portal.
Chapter 5. Documentation
- 3scale 2.13.1 introduces support for Red Hat OpenShift Container Platform (OCP) 4.12.
- You must upgrade to 3scale 2.13.1 before you upgrade to OCP 4.12.
Supported configurations
- Check the latest information about 3scale 2.13 supported configurations at the Red Hat 3scale API Management Supported Configurations website.
Security updates
- Check the latest information about 3scale 2.13 security updates in the Red Hat Product Advisories portal.
Erratas
- Advisory for the Container Images: RHEA-2022:8551
Upgrade guides
Check the procedures to upgrade your 3scale installation from 2.12 to 2.13, for the following deployments:
Making open source more inclusive
Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.