higress

higress-groupApache-2.0活跃维护有专家点评

基于 Envoy 的云原生 AI 网关，统一代理和路由大模型 API 与微服务流量，支持 AI 原生插件扩展。

🤖 AI Gateway | AI Native API Gateway

v2.2.6发布于 2026-11-10 02:48 UTC9,749star +22 / 7 天1,384fork同步于 2026-11-11 05:28 UTC

AI 网关 API 网关云原生 Envoy 流量路由

对比 GitHub 官网 ai-gateway ai-native api-gateway cloud-native envoy

专家点评

上手难度：进阶更新于 2026-11-11

在 K8s 入口层用 Envoy 统一代理 LLM API 和 MCP Server，替代自建 Nginx 加散装 SDK 转发

适用场景

多个大模型厂商的 API Key 需要集中管理和限流：把 OpenAI、通义、Claude 的调用统一收敛到网关，按租户或团队做配额和密钥轮换，比在每个服务里各写一套 SDK 转发逻辑更容易审计
AI Agent 需要调用一批内部 MCP Server：用它的插件机制托管 MCP Server，Agent 侧只认一个网关地址，省掉每个 Agent 单独配 MCP 连接和鉴权
已有 Istio/Envoy 服务网格，想在同一控制面下加 AI 流量：复用现有的 Gateway API、可观测性和证书体系，不用为 LLM 流量单独维护一套入口
流式对话场景需要网关不缓冲 SSE：它明确支持完整流式处理，普通反向代理在默认配置下容易把 SSE 攒成整包，首 token 延迟会明显变差

踩坑

镜像在阿里云区域仓库，非中国区节点拉取会超时，得手动换 us-west-1 或 ap-southeast-7 源；K8s 下还要通过 Helm 的 global.hub 覆盖仓库地址，这一步不配就会卡在 ImagePullBackOff
单机 all-in-one 只是试用形态，issue 里有 higress-controller 容器 unhealthy 导致启动失败的反馈，说明控制面和数据面的启动顺序、依赖健康检查在资源受限环境里不稳，上生产前要按 Helm 方式部署并确认各组件就绪
它建立在 Istio 和 Envoy 之上，排查问题最终会落到 Envoy 配置和 xDS 上；团队里没人熟悉这套栈时，出问题只能看控制台，定位深度有限

怎么上手

由 README 提炼，执行前请确认

原文

mkdir higress; cd higress
docker run -d --rm --name higress-ai -v ${PWD}:/data -p 8001:8001 -p 8080:8080 -p 8443:8443 higress-registry.cn-hangzhou.cr.aliyuncs.com/higress/all-in-one:latest

硬件要求按 README 说明

README 未说明具体 CPU/内存/显存要求；单机可用一条 Docker 命令启动，无需 GPU 即可运行网关本身。

有 Docker 镜像

下载：源码 zip·GitHub Releases（安装包）本站不镜像安装包

项目说明

由 README 自动翻译提炼

基于 Istio 和 Envoy 的云原生 AI 网关，统一管理 LLM API 与 MCP Server

基于 Envoy 的云原生 AI 网关，统一代理和路由大模型 API 与微服务流量，支持 AI 原生插件扩展。

核心能力

用统一协议接入国内外主流大模型厂商
通过插件机制托管 MCP Server 供 AI Agent 调用
支持 SSE 等流式协议的完整流式处理
用 Go/Rust/JS 编写 Wasm 插件热更新不丢流量
兼容 Ingress 与 Gateway API，可作 K8s 入口控制器

容易踩的坑

镜像托管在阿里云区域仓库，国内拉取超时需换 us-west-1 或 ap-southeast-7 镜像源；K8s 部署需通过 Helm 的 global.hub 指定镜像仓库；控制台在 8001 端口，网关 HTTP/HTTPS 分别是 8080 和 8443。

内容由模型根据 README 生成，可能不完整或不准确，以官方文档为准。看原文 README

最近发版

5 个版本v2.2.6

全部 release

v2.2.6最新正式版2026-11-10 · 2026-11-10 02:48 UTC
Higress

📋 Release Overview

This release includes 76 updates, covering feature enhancements, bug fixes, performance optimizations, and more.

Distribution of Updates
- New Features: 2
- Bug Fixes: 49
- Refactoring & Optimizations: 8
- Documentation Updates: 10
- Test Improvements: 7
📝 Full Changelog

🚀 New Features (Features)
- Related PR: #5328
  Contributor: @higress-release-automation[bot]
  Change Log: This PR prepares the plugin snapshot release v2.2.6 by introducing three core release metadata files (evidence, plans, snapshots) and updating the VERSION files for the ai-agent and ai-cache WASM plugins to ensure version consistency and traceability.
  Feature Value: Provides users with stable, verifiable candidate plugin versions, enhancing transparency and security in the release process; guarantees trusted plugin origins via SHA256 digests and commit references, facilitating auditing and rollback, and improving production deployment reliability.
- Related PR: #5263
  Contributor: @sunxia0
  Change Log: Introduces the server.passthroughInstructions configuration option to selectively forward upstream instructions strings in MCP proxy discovery responses; reuses existing RouteCall and authentication policies, extracting and injecting only valid instructions fields while safely ignoring invalid or oversized values.
  Feature Value: Enables flexible control over whether the MCP gateway proxy exposes upstream services’ raw instructions to clients, improving protocol compatibility and debugging capability; disabled by default to ensure security, while preserving existing proxy behavior to minimize upgrade risk.
🐛 Bug Fixes (Bug Fixes)
- Related PR: #5323
  Contributor: @johnlanni
  Change Log: Upgrades the Istio submodule to commit 383f79d, integrating an SRDS gateway cache fix: cache invalidation now depends only on the actually selected HTTP/HTTP3 gateways—modifications to unselected gateways precisely invalidate corresponding host cache entries, eliminating O(n²)-complexity cache invalidation overhead.
  Feature Value: Significantly improves route configuration propagation speed in large-scale Ingress scenarios, reduces gateway cache refresh latency, enhances Higress stability and responsiveness under high-concurrency multi-gateway environments, and improves user service deployment experience.
- Related PR: #5321
  Contributor: @johnlanni
  Change Log: Fixes a security vulnerability where path parameters in REST-to-MCP request URLs were not URL-encoded; introduces url.PathEscape for strict encoding of path segment parameters and adds multiple validation mechanisms to block bypass attempts (e.g., ../, %2e%2e); also introduces new template functions pathescape/queryescape and an allowUnsafePathArgs configuration toggle.
  Feature Value: Prevents unauthorized access and SSRF risks caused by malicious path parameters, improving MCP server security; users gain protection without modifying business logic, and legacy configurations remain compatible via explicit toggle, reducing upgrade cost and ensuring production stability.
- Related PR: #5317
  Contributor: @johnlanni
  Change Log: Fixes an issue where requests may hang indefinitely causing 503 errors when global concurrency limiting is enabled; modifies the asynchronous scheduling path to return HeaderStopAllIterationAndWatermark, ensuring requests correctly resume after evaluation completes.
  Feature Value: Prevents persistent 503 cluster_not_found errors after enabling global_inflight_enabled, improvin
v2.2.52026-10-04 · 2026-10-04 19:46 UTC
查看更新说明
Higress

📋 Overview of This Release

This release includes 133 updates, covering feature enhancements, bug fixes, performance optimizations, and more.

Distribution of Changes
- New Features: 21 items
- Bug Fixes: 72 items
- Refactoring & Optimizations: 6 items
- Documentation Updates: 32 items
- Test Improvements: 2 items
📝 Full Changelog

🚀 New Features (Features)
- Related PR: #4995
  Contributor: @johnlanni
  Change Log: This PR primarily completes the v2.2.5 release, updating the VERSION file and the appVersion field in helm/core and helm/higress/Chart.yaml, and synchronizing dependency versions in Chart.lock to ensure Helm Charts are aligned with plugin snapshots and the plugin-server image version.
  Feature Value: Provides users with a stable and reproducible v2.2.5 release package, unifying Helm Charts, plugin snapshots, and image versions—reducing deployment inconsistency risks and improving production environment version management reliability and upgrade experience.
- Related PR: #4971
  Contributor: @johnlanni
  Change Log: This PR re-triggers the plugin snapshot 2.2.5 release workflow by adding an empty commit, satisfying the promote workflow’s mandatory authorization requirement for non-author maintainers’ head commits—thus bypassing the automatic release block caused by missing valid reviews in #4968.
  Feature Value: Ensures compliance with permission governance policies, enhancing release reliability and audit compliance; enables users to promptly obtain the MCP-server 2.0.3-compatible plugin snapshot after formal review, avoiding functional delivery delays due to workflow anomalies.
- Related PR: #4938
  Contributor: @higress-release-automation[bot]
  Change Log: Updates the plugin release snapshot file, modifying the sourceCommit and baseCommit hash values for version 2.2.5 to ensure the snapshot content precisely corresponds to the specified code commit—establishing a verifiable and immutable release candidate.
  Feature Value: Guarantees reproducibility and trustworthiness of version releases, enabling users and maintainers to accurately trace build origins—improving transparency and security of the release process and reducing deployment risks caused by inconsistent commits.
- Related PR: #4937
  Contributor: @higress-release-automation[bot]
  Change Log: This PR prepares the 2.2.5 plugin snapshot release, updating the sourceCommit and baseCommit hash values in release/plans/2.2.5.json and release/snapshots/2.2.5.json to ensure traceable build sources and accurate, consistent version metadata.
  Feature Value: Ensures reproducibility and trustworthiness of plugin builds by pinning snapshot commit hashes—enabling users to accurately verify binary provenance, thereby enhancing release process security and compliance, and reducing version confusion risk.
- Related PR: #4934
  Contributor: @higress-release-automation[bot]
  Change Log: This PR prepares the plugin snapshot 2.2.5 release, updating three release metadata files (evidence, plans, and snapshots)—removing outdated commit references, previousRelease fields, and redundant verification information—to guarantee immutability and clear version origin and hash verification.
  Feature Value: Ensures traceability and integrity of plugin releases; users can verify download package authenticity via hash validation—avoiding deployment risks from version confusion or tampering—and enhancing production environment stability and security compliance.
- Related PR: [#4919](https://git
v2.2.42026-08-13 · 2026-08-13 23:49 UTC
查看更新说明
Higress

📋 Release Overview

This release includes 96 updates, covering feature enhancements, bug fixes, performance optimizations, and more.

Distribution of Changes
- New Features: 21 items
- Bug Fixes: 56 items
- Refactoring & Optimizations: 6 items
- Documentation Updates: 7 items
- Test Improvements: 6 items
📝 Complete Changelog

🚀 New Features (Features)
- Related PR: #4488
  Contributor: @higress-release-automation[bot]
  Change Log: This PR prepares the plugin snapshot for version 2.2.4 by adding four JSON snapshot files (bootstrap-evidence, evidence, plans, snapshots) to record version numbers, image references, SHA256 checksums, and commit information for AI Agent and other plugins. It also updates the ai-agent plugin’s VERSION from 2.0.0 to 2.0.1, ensuring build reproducibility and immutability.
  Feature Value: By generating immutable snapshots and standardizing version metadata, this enhancement improves the auditability, reproducibility, and security of plugin releases—enabling users to accurately verify plugin origin and integrity, reduce production deployment risks, and strengthen software supply chain trustworthiness.
- Related PR: #4451
  Contributor: @sunxia0
  Change Log: Introduces a collection of MCP protocol demonstration examples, including local Higress environments based on Kind and Helm, Wasm plugin build workflows, multi-version protocol support, and step-by-step demonstrations across multiple scenarios (HTTP, REST-to-MCP, modern-to-legacy bridging, request validation), accompanied by bilingual documentation and reproducible test assets.
  Feature Value: Provides developers with an out-of-the-box, reproducible hands-on guide for MCP protocol adoption—significantly lowering integration barriers. Standardized environments and comprehensive examples accelerate user understanding of protocol capabilities, compatibility verification, and rapid deployment of production-grade gateway extensions.
- Related PR: #4449
  Contributor: @johnlanni
  Change Log: Adds an immutable Go/Rust plugin automated release pipeline—including precise tag authorization, candidate version promotion, coordinated orchestration across plugin service/console/standalone modes, and generation of immutable release evidence. Multiple GitHub Actions workflows are refactored to support deterministic builds and snapshot validation.
  Feature Value: Delivers a stable, verifiable, tamper-proof plugin release mechanism for Higress users—substantially improving plugin distribution security and traceability. Mitigates production failures caused by version drift or erroneous releases and enhances reliability in enterprise-grade production environments.
- Related PR: #4318
  Contributor: @EndlessSeeker
  Change Log: Adds runtime support for Gateway API Inference Extension v1.4, including deterministic synthetic Service port generation, routing HTTPRoute backends to the first synthetic cluster port, and updating Envoy, go-control-plane, and Istio submodules to support served-endpoint metadata and data-parallel endpoint aggregation.
  Feature Value: Enables native Higress gateway compatibility with the Inference Extension v1.4 standard—improving unified access and traffic governance capability for AI/ML services in Kubernetes via the Gateway API. Reduces configuration complexity and operational overhead for deploying inference services.
- Related PR: #4306
  Contributor: @Aias00
  Change Log: Supports mixing HTTP/HTTPS target addresses in McpBridge, parsing the scheme from the `higress.io/de
v2.2.32026-06-25 · 2026-06-25 02:58 UTC
查看更新说明
Higress

📋 Overview of This Release

This release includes 48 updates, covering AI Gateway enhancements, multi-provider LLM protocol compatibility, gateway stability, Gateway API and Helm improvements, test coverage, and release maintenance.

Distribution of Updates
- New Features: 11 items
- Bug Fixes: 28 items
- Documentation Updates: 1 item
- Testing Improvements: 5 items
- Release and Dependency Maintenance: 3 items
📝 Full Change Log

🚀 New Features (Features)
- Related PR: #3849
  Contributor: @GHX5T-SOL
  Change Log: Key Auth now supports multiple credentials for a single service.
  Feature Value: Simplifies migration and multi-client access scenarios where more than one key must be managed for the same service.
- Related PR: #3838
  Contributor: @Betula-L
  Change Log: jwt-auth now supports remote JWKS.
  Feature Value: Makes centralized key management and key rotation easier for JWT-based authentication.
- Related PR: #3894
  Contributor: @JianweiWang
  Change Log: ai-security-guard adds structured x_higress deny responses, error-path metrics, and AI logging.
  Feature Value: Improves observability and policy feedback for AI content safety enforcement.
- Related PR: #3898
  Contributor: @zat366
  Change Log: ai-load-balancer adds a cluster_hash load balancing policy based on FNV-1a consistent hashing.
  Feature Value: Provides more stable routing across model backend clusters.
- Related PR: #3895
  Contributor: @JianweiWang
  Change Log: ai-security-guard adds Embedding API content detection support.
  Feature Value: Extends AI content safety checks beyond chat/completion-style requests.
- Related PR: #3916
  Contributor: @ponypony0123
  Change Log: model-router adds keepOriginalModelName to preserve the full original model name.
  Feature Value: Helps users keep downstream model identity semantics intact while still applying model routing rules.
- Related PR: #3979
  Contributor: @EndlessSeeker
  Change Log: Helm now supports skipping IngressClass creation.
  Feature Value: Better supports clusters where IngressClass resources are pre-managed or controlled by platform teams.
- Related PR: #3981
  Contributor: @EndlessSeeker
  Change Log: GatewayClass isolation is now configurable.
  Feature Value: Gives operators more control over resource boundaries in multi-GatewayClass environments.
- Related PR: #3943
  Contributor: @zijiren233
  Change Log: Enhanced SSL passthrough support.
  Feature Value: Improves Higress support for TLS passthrough scenarios.
- Related PR: #3989
  Contributor: @Rand01ph
  Change Log: AI Proxy adds vLLM passthrough support for Anthropic Messages and newer OpenAI endpoints.
  Feature Value: Improves compatibility for users running vLLM behind Higress as an AI gateway.
- **Related
v2.2.22026-05-26 · 2026-05-26 01:41 UTC
查看更新说明
Higress

📋 Overview of This Release

This release includes 37 updates, covering feature enhancements, bug fixes, performance optimizations, and more.

Distribution of Updates
- New Features: 13 items
- Bug Fixes: 18 items
- Documentation Updates: 5 items
- Testing Improvements: 1 item
📝 Full Change Log

🚀 New Features (Features)
- Related PR: #3827
  Contributor: @rinfx
  Change Log: Added the modelToHeader configuration option, with default value x-higress-llm-model-final; synchronously updates this header after parsing the newModel from the request body to ensure downstream logic such as rate limiting and metering aligns with the model mapping result; calls DisableReroute when reading the body to prevent routing conflicts.
  Feature Value: Enhances model routing consistency and reliability, enabling fallback, model-based rate limiting, and metering features to accurately reflect the actual matched model; users gain more stable and precise model dispatching capabilities without modifying business logic, reducing the risk of policy deviation caused by header synchronization issues.
- Related PR: #3823
  Contributor: @johnlanni
  Change Log: Introduced an nginx-rewrite-compatible WASM plugin that implements compatible parsing of Nginx rewrite + set semantics, securely executes rewriting logic within a WASM sandbox to avoid the CVE-2026-42945 heap overflow vulnerability, and supports path matching, variable capture, and substitution.
  Feature Value: Enables Higress users to smoothly migrate existing Nginx rewrite rules while ensuring compatibility and eliminating critical security risks, lowering the refactoring cost and operational risk for legacy services transitioning from Nginx to Higress.
- Related PR: #3820
  Contributor: @wydream
  Change Log: Refactored the /v1/messages request handling for the Bedrock Provider: replaced the original two-layer protocol conversion chain (OpenAI → Converse) with direct connectivity to the native Bedrock Mantle Anthropic Messages API; added support for the Mantle endpoint, restructured request routing logic, and extended capability declarations.
  Feature Value: Delivers lower latency, higher compatibility, and native Anthropic feature support (e.g., tool use, beta headers) for /v1/messages calls; avoids semantic loss and performance overhead associated with protocol translation, significantly improving the Bedrock integration experience and stability.
- Related PR: #3766
  Contributor: @rinfx
  Change Log: Added support for cached token usage (CacheReadInputTokens) in the streaming response transformation logic from OpenAI to Claude; modified core transformer code and added corresponding unit test cases to ensure the Claude compatibility layer accurately conveys cached token count information.
  Feature Value: Enables AI agents to correctly report input token savings resulting from cache hits when invoking Claude models, helping users precisely monitor and optimize API costs; simultaneously improves transparency and billing consistency across multi-model metering, enhancing enterprise-grade usage analytics capabilities.
- Related PR: #3748
  Contributor: @zat366
  Change Log: Added the enable_path_suffixes configuration option to the QuotaConfig struct to support custom path suffix matching; updated configuration parsing logic to handle default values; modified the getOperationMode function to accommodate the new path suffix logic; enhanced test coverage for the new configuration and its impact on ope

用户点评

登录用户的真实使用记录，可按版本和硬件筛选

共 0 条

还没有人点评。第一个说出真实体验的人最有价值。

README 原文

未翻译

在 GitHub 打开

What is Higress?

Higress is a cloud-native API gateway based on Istio and Envoy, which can be extended with Wasm plugins written in Go/Rust/JS. It provides dozens of ready-to-use general-purpose plugins and an out-of-the-box console (try the demo here).

Core Use Cases

Higress's AI gateway capabilities support all mainstream model providers both domestic and international. It also supports hosting MCP (Model Context Protocol) Servers through its plugin mechanism, enabling AI Agents to easily call various tools and services. With the openapi-to-mcp tool, you can quickly convert OpenAPI specifications into remote MCP servers for hosting. Higress provides unified management for both LLM API and MCP API.

🌟 Try it now at https://mcp.higress.ai/ to experience Higress-hosted Remote MCP Servers firsthand:

Higress MCP Server Platform

Production Adoption

Higress originated at Alibaba to address long-connection disruption during gateway reloads and improve gRPC/Dubbo load balancing. It is now developed as a vendor-neutral CNCF project and is used by organizations across multiple industries. Public adopters and their use cases are listed in ADOPTERS.md.

Quick Start

Higress can be started with just Docker, making it convenient for individual developers to set up locally for learning or for building simple sites:

# Create a working directory
mkdir higress; cd higress
# Start higress, configuration files will be written to the working directory
docker run -d --rm --name higress-ai -v ${PWD}:/data \
        -p 8001:8001 -p 8080:8080 -p 8443:8443  \
        higress-registry.cn-hangzhou.cr.aliyuncs.com/higress/all-in-one:latest

Port descriptions:

Port 8001: Higress UI console entry
Port 8080: Gateway HTTP protocol entry
Port 8443: Gateway HTTPS protocol entry

Higress publishes project images through dedicated regional registry endpoints. Operators may mirror the images to a registry they control and configure the Helm global.hub value accordingly.

If you experience a timeout when pulling image from higress-registry.cn-hangzhou.cr.aliyuncs.com, you can try replacing it with the following docker registry mirror source:

North America: higress-registry.us-west-1.cr.aliyuncs.com

Southeast Asia: higress-registry.ap-southeast-7.cr.aliyuncs.com

For Kubernetes deployments, you can configure the global.hub parameter in Helm values to use a mirror registry closer to your region. This applies to both Higress component images and built-in Wasm plugin images:
# Example: Using North America mirror
helm install higress -n higress-system higress.io/higress --set global.hub=higress-registry.us-west-1.cr.aliyuncs.com --create-namespace
Available mirror registries:

China (Hangzhou): higress-registry.cn-hangzhou.cr.aliyuncs.com (default)

North America: higress-registry.us-west-1.cr.aliyuncs.com

Southeast Asia: higress-registry.ap-southeast-7.cr.aliyuncs.com

For other installation methods such as Helm deployment under K8s, please refer to the official Quick Start documentation.

Use Cases

MCP Server Hosting:

Higress hosts MCP Servers through its plugin mechanism, enabling AI Agents to easily call various tools and services. With the openapi-to-mcp tool, you can quickly convert OpenAPI specifications into remote MCP servers.

Key benefits of hosting MCP Servers with Higress:
- Unified authentication and authorization mechanisms
- Fine-grained rate limiting to prevent abuse
- Comprehensive audit logs for all tool calls
- Rich observability for monitoring performance
- Simplified deployment through Higress's plugin mechanism
- Dynamic updates without disruption or connection drops
  
  Learn more...
AI Gateway:

Higress connects to all LLM model providers using a unified protocol, with AI observability, multi-model load balancing, token rate limiting, and caching capabilities:

Higress is also listed as a conformant Gateway API Inference Extension implementation, supporting inference-aware routing on Kubernetes.
Kubernetes ingress controller:

Higress can function as a feature-rich ingress controller and is listed in the official Kubernetes Ingress Controllers documentation. It is compatible with many annotations of the Kubernetes NGINX Ingress Controller.

Higress supports the Gateway API standard and is listed as a conformant Gateway API implementation, enabling smooth migration from the Ingress API to the Gateway API.

Compared to ingress-nginx, the resource overhead has significantly decreased, and the speed at which route changes take effect has improved by ten times.

The following resource overhead comparison comes from sealos.

For details, you can read this article to understand how sealos migrates the monitoring of tens of thousands of ingress resources from nginx ingress to higress.
Microservice gateway:

Higress can function as a microservice gateway, which can discovery microservices from various service registries, such as Nacos, ZooKeeper, Consul, Eureka, etc.

It deeply integrates with Dubbo, Nacos, Sentinel and other microservice technology stacks.
Security gateway:

Higress can be used as a security gateway, supporting WAF and various authentication strategies, such as key-auth, hmac-auth, jwt-auth, basic-auth, oidc, etc.

Core Advantages

Production Grade

Born from Alibaba's internal product with over 2 years of production validation, supporting large-scale scenarios with hundreds of thousands of requests per second.

Completely eliminates traffic jitter caused by Nginx reload, configuration changes take effect in milliseconds and are transparent to business. Especially friendly to long-connection scenarios such as AI businesses.
Streaming Processing

Supports true complete streaming processing of request/response bodies, Wasm plugins can easily customize the handling of streaming protocols such as SSE (Server-Sent Events).

In high-bandwidth scenarios such as AI businesses, it can significantly reduce memory overhead.
Easy to Extend

Provides a rich official plugin library covering AI, traffic management, security protection and other common functions, meeting more than 90% of business scenario requirements.

Focuses on Wasm plugin extensions, ensuring memory safety through sandbox isolation, supporting multiple programming languages, allowing plugin versions to be upgraded independently, and achieving traffic-lossless hot updates of gateway logic.
Secure and Easy to Use

Based on Ingress API and Gateway API standards, provides out-of-the-box UI console, WAF protection plugin, IP/Cookie CC protection plugin ready to use.

Supports connecting to Let's Encrypt for automatic issuance and renewal of free certificates, and can be deployed outside of K8s, started with a single Docker command, convenient for individual developers to use.

Community

Join our Discord community! This is where you can connect with developers and other enthusiastic users of Higress.

Join the monthly Higress Community Meeting for public project updates, technical discussions, roadmap planning, and community questions.

The complete inventory of public and private communication channels, subproject channels, meeting information, and contributor activity is in COMMUNITY.md.

Code of Conduct

The Higress community follows the CNCF Code of Conduct. The project's adopted Code of Conduct is documented in CODE_OF_CONDUCT.md. Please review it before participating in the community.

Governance & Maintainers

Project governance, the maintainer roster, and the contribution model are described in GOVERNANCE.md and MAINTAINERS.md. New contributors are encouraged to start with CONTRIBUTING_EN.md. Forward planning and release procedures are documented in ROADMAP.md and RELEASE.md.

Security

Please report security vulnerabilities following the process described in SECURITY.md.

Thanks

Higress would not be possible without the valuable open-source work of projects in the community. We would like to extend a special thank you to Envoy and Istio.

Related Repositories

Higress Console: https://github.com/higress-group/higress-console
Higress Standalone: https://github.com/higress-group/higress-standalone
Higress Plugin Server: https://github.com/higress-group/plugin-server
Higress Wasm Plugin Golang SDK: https://github.com/higress-group/wasm-go

Contributors

Star History

Cloud Native Computing Foundation

We are a Cloud Native Computing Foundation sandbox project.

The Linux Foundation® (TLF) has registered trademarks and uses trademarks. For a list of TLF trademarks, see Trademark Usage.

Copyright Higress a Series of LF Projects, LLC. For website terms of use, trademark policy and other project policies please see https://lfprojects.org/policies/.

专家点评

适用场景

踩坑

同类对比

怎么上手

项目说明

核心能力

容易踩的坑

最近发版

Higress

📋 Release Overview

Distribution of Updates

📝 Full Changelog

🚀 New Features (Features)

🐛 Bug Fixes (Bug Fixes)

Higress

📋 Overview of This Release

Distribution of Changes

📝 Full Changelog

🚀 New Features (Features)

Higress

📋 Release Overview

Distribution of Changes

📝 Complete Changelog

🚀 New Features (Features)

Higress

📋 Overview of This Release

Distribution of Updates

📝 Full Change Log

🚀 New Features (Features)

Higress

📋 Overview of This Release

Distribution of Updates

📝 Full Change Log

🚀 New Features (Features)

用户点评

README 原文

What is Higress?

Core Use Cases

Production Adoption

Summary

Quick Start

Use Cases

Core Advantages

Community

Code of Conduct

Governance & Maintainers

Security

Thanks

Related Repositories

Contributors

Star History

Cloud Native Computing Foundation

相关项目