Releases: alibaba/higress
v1.0.0
这是 Higress 的首个正式 GA 版本。欢迎大家试用。如有任何问题,请在 Issues 或 Discussions 里提出。
版本变化:
Higress Core:
功能优化:
- 支持加载包含多于两层数据的 Wasm 插件 OCI 镜像 #244
- 支持在转发请求和响应时对 HTTP 标头进行增删改操作 #254
- 支持在转发请求时重写请求路径 #278
- 支持在全局、域名和路由粒度禁用指定的 Wasm 插件 #255
- 支持使用
global.localHelm 参数启用本地运行模式 #269 - 支持限定仅监听部分命名空间下的 Ingress 资源以满足单个 K8s 集群多实例部署的需求 #280
问题修复:
- 修复无法正常从 Apache ZooKeeper 中读取服务注册信息的问题 #253
- 在低于 1.21.0 版本的 K8s 集群中默认只用
first-party-jwt认证模式,修复由于 K8s 本身不支持third-party-jwt而导致的功能问题 #266 - 修复使用路径前缀匹配模式时“不区分大小”写功能不工作的问题 #260
- 修复在系统内核版本低于 4.11.0 的 K8s 集群上无法正常运行的问题 #301
不兼容改动:
- 变更接入 Skywalking 所需的 Helm 配置模型 #333
Higress Console:
功能优化:
- 支持在路由上配置请求重写、请求头操作、请求重试、跨域等路由策略 #198 #199 #201
- 支持在全局、域名和路径等多层级继承 Wasm 插件配置,并在内置一系列插件的基础上,允许用户配置自定义的 Wasm 插件:#198 #199 #200 #201
- 支持用户通过 Helm 参数自定义监控套件所使用的存储类型 #204
- 支持自动升级内置监控看板的视图配置 #217
问题修复:
- 修复对接 Apache Zookeeper 数据来源时的一些兼容性问题 #203
- 修复监控看板页面在显示时可能出现循环嵌套问题 #205
- 在单一服务名称和端口同时提供 TCP 和 UDP 协议访问时的界面展示问题 #209
- 修复删除资源 API 返回的 HTTP 状态码错误的问题 #213
- 修复启用监控套件后无法通过
helm upgrade命令升级集群的问题 #218
感谢所有为此版本做出贡献的同学:@2456868764 @casun18 @CH3CHO @Charlie17Li @Fkbqf @johnlanni @OnlyPiglet @rinfx @songpengyuan @SpecialYang @tomkerkhove @WeixinX @Xunzhuo @zhangjiahaol
This is the first GA release of Higress. You are welcomed to have a try. If there are any questions or suggestions, please post them in Issues or Discussions.
Version Changes:
Higress Core:
Features:
- Support Wasm plugin OCI images containing more than two layers #244
- Support adding, modifying and deleting HTTP headers when forwarding requests and responses #254
- Support rewriting request path when forwarding requests #278
- Support toggling Wasm plugins on following levels: global, domain, route #255
- Support enabling local mode with Helm property
global.local#269 - Allow watching Ingress resources in a specific namespace, so multiple Higress instances can be deployed within a single K8s cluster #280
Fixes:
- Fix the bug that unable to load registered services from Apache Zookeeper #253
- Use
first-party-jwtauthentication mode by default in K8s clusters with version < 1.21.0, to fix the malfuction caused by the unsupport ofthird-party-jwtmode #266 - Fix the malfunction of "ignoreUriCase" function when matching it by prefix #260
- Fix the pod initializing error in K8s clusters with kernal version lower than 4.11.0 #301
Incompatibles:
- Use new configuration properties to enable Skywalking integration #333
Higress Console:
Features:
- Support configuring strategy on routes: rewrite, header control, retry and CORS #198 #199 #201
- Add Wasm plugin configuration support on following levels: global, domain and route. Besides a series of built-in plugins, user can also configure custom plugins. #198 #199 #200 #201
- Allow customizing storageClass used by the built-in o11y suite via Helm properties #204
- Support upgrading built-in dashboard configurations automatically #217
Fixes:
- Fix some compatibility issues in Apache Zookeeper integration #203
- Fix a possible nesting display issue on the dashboard page #205
- Fix UI display issues when a host:port combination of service supports TCP and UDP protocols at the same time #209
- Fix the incorrect response status code returned by DELETE APIs #213
- Fix the malfunction of
helm upgradecommands based on an o11y-enabled installation #218
Higress would like to thank the following contributors for their contributions to this release: @2456868764 @casun18 @CH3CHO @Charlie17Li @Fkbqf @johnlanni @OnlyPiglet @rinfx @songpengyuan @SpecialYang @tomkerkhove @WeixinX @Xunzhuo @zhangjiahaol
v0.7.3
v1.0.0-rc
v0.7.2
v0.7.1
改动:
- Feature: 支持基于静态IP或者DNS发现的服务发现机制
- Feature: 支持识别 K8s 版本选择对应的控制面认证方式(JWT policy)
- Bugfix:修复
higress.io/destination注解对于 Dubbo 服务端口的解析错误
What's Changed:
- Feature: Support service discovery based on static IP or DNS.
- Feature: Support identifying the K8s version and selecting the corresponding control plane authentication method (JWT policy)
- Bugfix: Fix the parsing error of
higress.io/destinationannotation for Dubbo service port
v0.7.0
从这个版本开始, 通过 Helm 安装/升级 Higress 会自动安装适配好版本的 Higress Console,若无需控制台功能,也可以直接安装 Higress Core
版本变化:
Higress Core:
- 支持 Istio CRD,可以替代 istio ingress gateway,通过 helm 参数
--set enableIstioAPI=true开启 #243 - 增加了多种路由匹配的Ingress注解 ,并实现了多条件下的路由匹配顺序机制 #240 #214 #188 #174
- 支持对接 SkyWalking 的监控指标收集 #238
Higress Console:
- 具备登陆认证能力
- 集成 grafana 可观测大盘
- 具备完整的路由管控功能
- 具备K8s/Nacos/ZK三种服务来源配置
- 具备基础的域名策略能力:开启/关闭 TLS,强制 HTTPS
- 具备TLS证书基础管理能力
感谢所有为此版本做出贡献的同学:@Charlie17Li @Xunzhuo @CH3CHO @songpengyuan @wojesen @jameszhangyukun @Risker-C @Hinsteny @cobb-tx @PerforMance308 @dspo @whalecold @wangshiqi308 @dspo
Starting from this version, installing/upgrading Higress through Helm will automatically install the adapted version of Higress Console. If you don't need the console function, you can also install Higress Core directly
Version changes:
Higress Core:
- Support Istio CRD, which can replace the istio ingress gateway, and enable it through the helm parameter
--set enableIstioAPI=true#243 - Added the Ingress annotation for multi-route matching, and realized the route matching sequence mechanism under multiple conditions #240 #214 #188 #174
- Support SkyWalking metrics #238
Higress Console:
- Support login authentication
- Integrated grafana dashboard
- Support complete routing control
- Support K8s/Nacos/ZK service source configuration
- Support basic domain policy capabilities: enable/disable TLS, enforce HTTPS
- Support TLS certificate basic management capabilities
v0.6.2
v0.6.1
改动:
- Feature: helm 安装的默认行为改为只监听 ingressClass 为
higress的 ingress,避免与其他 ingress controller 产生冲突
What's Changed:
- Feature: The default behavior of helm installation is changed to only listen to the ingress whose ingressClass is
higressto avoid conflicts with other ingress controllers
v0.6.0
改动:
- Feature: 提供开启或关闭 Service Mesh 支持的两种部署模式,关闭模式下不再需要安装 Istio #140
- Feature:实现 e2e 测试框架,并实现了通过 PR 自动触发的 e2e 集成测试,感谢 @Xunzhuo 极致的工作 #124 #135
- Feature:提供了 Higress WasmPlugin API,在 Istio API 基础上扩展了路由/域名级生效的配置字段 #129
What's Changed:
- Feature: Provides two deployment modes to enable or disable Service Mesh support. Istio no longer needs to be installed in the disabled mode #140
- Feature: Implemented the e2e testing framework, and realized the e2e integration test triggered automatically by PR, thanks to @Xunzhuo for his excellent work #135
- Feature: Provides the Higress WasmPlugin API, which extends the configuration fields that take effect at the routing/domain level based on the Istio API #129
v0.5.3
改动:
- Feature: 支持 Ingress 对接 Nacos/ZooKeeper 进行服务发现 #108 , 示例配置
- Feature:定义 McpBridge API 支持对接多种注册中心进行服务发现,感谢 @NameHaibinZhang #107
- Feature:支持 hostNetwork 模式部署,感谢 @iutx 的PR #96
- Feature: 支持 third-party-jwt 模式对接 istio,感谢 @xcbeyond 的PR #93
What's Changed:
- Feature: Support Ingress to connect to Nacos/ZooKeeper for service discovery #108
- Feature: Define McpBridge API to support docking with multiple registries for service discovery,thanks to @NameHaibinZhang #107
- Feature: Support hostNetwork mode deployment,thanks to @iutx #96
- Feature: Support third-party-jwt mode docking istio,thanks to @xcbeyond #93