v2.0.3
higress-group/higressv2.0.3Nov 8, 2024by johnlanni
AI Summary
This version addresses a breaking change regarding Gateway API configuration and adjusts the default fail strategy for WASM plugins to prevent errors during configuration parsing.
Key Highlights
- Fixed Gateway API listening behavior based on Helm parameters.
- Adjusted default WASM plugin fail strategy to FAIL_OPEN.
Breaking Changes
- Fixed Gateway API listening behavior based on Helm parameters (change default fail strategy to FAIL_OPEN)
New Features
- Redis call support with Rust WASM
- Multiple version capability for routes
- Downstream and upstream configuration via Helm parameters
- Lazy formatted log
Full Release Notes
## Notices ### Breaking Change The issue introduced from 2.0.0, where it still listened to the Gateway API even when the helm parameter `global.enableGatewayAPI` was set to false, has been corrected in this version. If you have already used the Gateway API in your cluster, please force set this parameter to true in the values.yaml during the upgrade to avoid the situation where it no longer listens to the Gateway API after the upgrade. ### Recommended Upgrade Reasons In the previous 2.x versions of Higress Console, when deploying the WASM plugin, the default [fail strategy](https://istio.io/latest/docs/reference/config/proxy_extensions/wasm-plugin/#FailStrategy) was FAIL_CLOSE, which could lead to issues such as the gateway generating 503 errors and NFCF 500 errors if the plugin configuration parsing failed. This version has adjusted the fail strategy to FAIL_OPEN. However, we still recommend keeping the fail strategy as FAIL_CLOSE for plugins that require strict authentication, to avoid skipping permission checks due to plugin logic problems. ## What's Changed * fix destinationrule merge logic by @johnlanni in https://github.com/alibaba/higress/pull/1439 * feat: lazy formatted log by @jizhuozhi in https://github.com/alibaba/higress/pull/1441 * [feat] Support redis call with wasm-rust by @007gzs in https://github.com/alibaba/higress/pull/1417 * Fix the issue where wasmplugin does not work when kingress exists by @johnlanni in https://github.com/alibaba/higress/pull/1450 * fix: Control gateway-api Listener with global.enableGatewayAPI in Helm by @hanxiantao in https://github.com/alibaba/higress/pull/1461 * feat:Support downstream and upstram, which can be configured through helm parameters by @littlejiancc in https://github.com/alibaba/higress/pull/1399 * modify log-format, then every plugin log is associated with access log by @rinfx in https://github.com/alibaba/higress/pull/1454 * Ai data mask deny word match optimize by @007gzs in https://github.com/alibaba/higress/pull/1453 * move nottinygc to proxy-wasm-go-sdk by @johnlanni in https://github.com/alibaba/higress/pull/1477 * add clusterrole for gateway api by @johnlanni in https://github.com/alibaba/higress/pull/1480 * feat: 🎸 Support for multiple version capability: Map different `Version` versions according to different routes by @heimanba in https://github.com/alibaba/higress/pull/1429 * feat: Update istio codebase by @CH3CHO in https://github.com/alibaba/higress/pull/1485 * Implement Rust Wasm Plugin Build & Publish Action by @007gzs in https://github.com/alibaba/higress/pull/1483 * update rust makefile by @johnlanni in https://github.com/alibaba/higress/pull/1491 * feat: Ensure all images are loaded to K8s before starting e2e tests by @CH3CHO in https://github.com/alibaba/higress/pull/1389 * docs: Added back to top , contributors section and star history graph by @Ranjana761 in https://github.com/alibaba/higress/pull/1440 * add textin embedding for ai-cache by @Chi-Kai in https://github.com/alibaba/higress/pull/1493 * release 2.0.3 by @johnlanni in https://github.com/alibaba/higress/pull/1494 ## New Contributors * @littlejiancc made their first contribution in https://github.com/alibaba/higress/pull/1399 * @Ranjana761 made their first contribution in https://github.com/alibaba/higress/pull/1440 **Full Changelog**: https://github.com/alibaba/higress/compare/v2.0.2...v2.0.3