3.2.1

Bug Fixes

• We've fixed a bug where APIRules v2alpha1 and v2 were set to the Error state when the target workload was in the mesh with the Istio proxy running in native sidecar mode. See #2100.
• We've fixed a bug that caused AuthorizationPolicy creation to fail for APIRules in namespaces with names longer than 36 characters. Now, namespace names up to 63 characters are supported. #2143

Full changelog: 3.2.0...3.2.1

3.1.4

Bug Fixes

• We've fixed a bug where APIRules v2alpha1 and v2 were set to the Error state when the target workload was in the mesh with the Istio proxy running in native sidecar mode. See #2100.
• We've fixed a bug that caused AuthorizationPolicy creation to fail for APIRules in namespaces with names longer than 36 characters. Now, namespace names up to 63 characters are supported. #2143

Full changelog: 3.1.3...3.1.4

3.2.0

APIRule v1beta1 Deletion

Version 3.2.0 of the API Gateway module introduces the first step in the process of deleting APIRule v1beta1. Now, Kyma dashboard does not display APIRule custom resources (CRs) in version v1beta1. All APIRules v1beta1 are fully operational from the command line, and you are still able to manage them using kubectl. Additionally, this change does not affect any pipelines that manage APIRules using Kubernetes utilities such as kubectl or helm.

Required action: You must migrate all your APIRules to version v2. For more information, see APIRule Migration. We strongly recommend starting the migration as soon as possible to avoid any disruptions. For the complete deletion timeline for SAP BTP, Kyma runtime, see APIRule Migration Timeline.

Bug Fixes

• We've fixed conversion from APIRule v1beta1 to v2. The conversion now sets all convertible fields in the APIRule's spec. #1983

Full changelog: 3.1.0...3.2.0

3.1.3

Changes

• Now, APIRules v1beta1 that are not migrated to version v2 are in the Warning state.
• In the controller, the deployed images are now provided using environment variables.

Full changelog: 3.1.2...3.1.3

3.1.2

Bug Fixes

• We've fixed zero downtime migration progressing in cases where an error occurs during the process. #2041

Full changelog: 3.1.1...3.1.2

3.1.1

Bug Fixes

• We've fixed conversion from APIRule v1beta1 to v2. The conversion now sets all convertible fields in the APIRule's spec. #1983

Full changelog: 3.1.0...3.1.1

3.1.0

Release 3.1.0 of the API Gateway module changes the stored version of APIRule to v2alpha1. This change is part of the migration process towards the v2 version, which will eventually result in removing the v1beta1 version. #1777

Bug Fixes

• Fix behaviour of in-cluster connectivity when using JWT handler in APIRule. Now, in-cluster connectivity is blocked. #1823
• Fix the extAuth handler not being scoped to a particular host. #1901
• Fix reconciliation of convertible APIRules. #1924
• When converting APIRule to version v2, the original-version annotation is not set if it's already present in the APIRule. #1921
• The order of rules in the APIRule Custom Resource is important. Rules defined earlier in the list have a higher priority than those defined later. For more information, see Significance of Rule Path Order. #1860

Full changelog: 3.0.0...3.1.0

3.0.4

Bug Fixes

• Unify Extensibility views for APIGateway and APIRule in Busola. #1927
• The order of rules in the APIRule Custom Resource is important. Rules defined earlier in the list have a higher priority than those defined later. For more information, see Significance of Rule Path Order. #1860

Full changelog: 3.0.3...3.0.4

3.0.3

Bug Fixes

• Fix the extAuth handler not being scoped to a particular host. #1931
• Fix reconciliation of convertible APIRules. #1925
• When converting APIRule to version v2, the original-version annotation is not set if it's already present in the APIRule. #1928

Full changelog: 3.0.2...3.0.3

3.0.2

Bug Fixes

• Fix behaviour of in-cluster connectivity when using JWT handler in APIRule. Now, in-cluster connectivity is blocked. #1868
• Now, when you create an APIRule with the noAuth access strategy, it is validated if the target workload has an Istio sidecar proxy injected. #1890
• Add a missing deprecation message when using k8s API to interact with APIRule v1beta1 CRs. Now, the following deprecation message is presented during each call: Warning: Version v1beta1 of APIRule is deprecated and will be removed in future releases. Use version v2 instead.. #1837

Full changelog: 3.0.1...3.0.2