2.10.2

New Features

• We've implemented a faster requeue when the error object has been modified occurs #1496
• We've added full support for special characters in asterisk paths #1569

Full changelog: 2.10.1...2.10.2

2.10.1

New Features

• Add issuerRef: garden to kyma-tls-cert certificate's spec 1529
• Change PodDisruptionBudget from minAvailable: 1 to maxUnavailable: 1 #1527

Full changelog: 2.10.0...2.10.1

2.10.0

New Features

• Introduce deprecation banner for v1beta1 APIRules #1448
• Add zone-based podAntiAffinity rules for the ory-oathkeeper Deployment. #1463

Full changelog: 2.9.0...2.10.0

2.9.0

New Features

• Introduce support for the path operators {*} and {**}#1397

Full changelog: 2.8.0...2.9.0

2.8.0

New Features

• Increase certificate key size of kyma-gateway to 4096 #1357
• Add support for APIRule V2alpha1 in the UI #1374

Bug fixes

• Remove hard dependency to Gardener DNSEntry and Certificate resources and handle them on-demand if they are present #1341
• Fix FQDN validation for the hosts field entries in APIRule v2alpha1, allowing for one-character long labels and two-character top-level domains #1376

Full changelog: 2.7.0...2.8.0

2.7.0

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

2.6.0

New Features

• Support for ExtAuth authorization in v2alpha1 APIRules #1258
• The UI displays a warning if an APIRule specifies a Gateway that is not in the correct format #1214

Full changelog: 2.5.0...2.6.0

2.5.0

New Features

• Add support for request modifiers in v2alpha1 APIRule #1207
• Add Gateway validation #1210

Full changelog: 2.4.2...2.5.0

2.4.2

Bug fixes

• Enhance the resilience of the API Gateway module's operator through optimizations and bug fixes.

Full changelog: 2.4.1...2.4.2

2.4.1

Fixed Bugs

• Bump golang version to 1.22.5 and k8s.io modules to v0.30.3 #1185
• Fix missing port name in webhook manifest #1189

Full changelog: 2.4.0...2.4.1