Skip to content

2.7.0
Compare
Choose a tag to compare
@github-actions github-actions released this 02 Oct 15:27
· 200 commits to main since this release
2.7.0
bf6e815
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Release 2.7 of the API Gateway module includes the fully functional version of APIRule v2alpha1 with noAuth, jwt, and extAuth access strategies. Version v2alpha1 is not meant for use in a production environment but for testing purposes only. After the testing phase, this version of APIRule is expected to be promoted to stable version v2 without significant changes.

For SAP BTP, Kyma runtime, API Gateway 2.7 is scheduled to be rolled out to the regular channel on October 28, 2024. After this date, users will be required to start testing the migration procedure. To learn more, see the APIRule migration blog post. It provides the timeline for deletion of APIRule v1beta1 and covers the following migration scenarios:
- From the noop, allow, or no_auth handler in version v1beta1 to the noAuth handler in version v2alpha1
- From the jwt handler in version v1beta1 to the new configuration of the jwt handler in version v2alpha1
The migration procedure from OAuth2 handlers based on Ory Oathkeeper to the new extAuth handler will be published in the next blog post. For now, see the tutorial Exposing a Workload with extAuth.

Deprecation

  • This release introduces the deprecation of the APIRule custom resource in version v1beta1.

New Features

  • We've added support for short host name for APIRule in version v2alpha1 (#1311). If you only provide the leftmost label in the spec.hosts field of an APIRule CR, it uses the domain name from the referenced Gateway, expanding the host to <label>.<gateway domain>. See Sample Custom Resources.

Bug Fixes

  • We've fixed the wildcard path format and the validation of the rule path in an APIRule (#1285).

Full changelog: 2.6.0...2.7.0

Assets 4
Loading