This is an automated email from the ASF dual-hosted git repository.
xuetaoli pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/dubbo-website.git
The following commit(s) were added to refs/heads/master by this push:
new f9b4054192c Remove mesh docs part and update pixiu gateway docs (#3191)
f9b4054192c is described below
commit f9b4054192cece41f933d85d0f8a10ee5e29aaf4
Author: Joe Zhong <[email protected]>
AuthorDate: Fri Feb 13 10:29:13 2026 +0800
Remove mesh docs part and update pixiu gateway docs (#3191)
---
content/en/overview/mesh/_index.md | 49 -----
content/en/overview/mesh/concepts/_index.md | 44 -----
content/en/overview/mesh/concepts/observability.md | 10 -
content/en/overview/mesh/concepts/security.md | 135 -------------
.../overview/mesh/concepts/traffic-management.md | 149 --------------
content/en/overview/mesh/getting-started.md | 59 ------
content/en/overview/mesh/setup/_index.md | 10 -
content/en/overview/mesh/setup/install/_index.md | 10 -
content/en/overview/mesh/setup/install/dubboctl.md | 56 ------
content/en/overview/mesh/setup/install/helm.md | 57 ------
.../overview/mesh/setup/install/platform/_index.md | 10 -
content/en/overview/mesh/tasks/_index.md | 45 -----
.../en/overview/mesh/tasks/observability/_index.md | 12 --
content/en/overview/mesh/tasks/security/_index.md | 12 --
.../mesh/tasks/traffic-management/_index.md | 28 ---
.../tasks/traffic-management/ingress/_index.md | 28 ---
.../traffic-management/ingress/gateway-api.md | 71 -------
content/en/overview/mesh/upgrade/_index.md | 10 -
content/en/overview/reference/_index.md | 2 +-
content/zh-cn/overview/mesh/_index.md | 16 --
content/zh-cn/overview/mesh/concepts/_index.md | 44 -----
.../zh-cn/overview/mesh/concepts/observability.md | 8 -
content/zh-cn/overview/mesh/concepts/security.md | 14 --
.../overview/mesh/concepts/traffic-management.md | 15 --
content/zh-cn/overview/mesh/getting-started.md | 53 -----
.../zh-cn/overview/mesh/setup/install/_index.md | 10 -
.../zh-cn/overview/mesh/setup/install/dubboctl.md | 43 -----
content/zh-cn/overview/mesh/setup/install/helm.md | 50 -----
.../overview/mesh/setup/install/platform/_index.md | 8 -
content/zh-cn/overview/mesh/tasks/_index.md | 43 -----
.../overview/mesh/tasks/observability/_index.md | 9 -
.../zh-cn/overview/mesh/tasks/security/_index.md | 9 -
.../mesh/tasks/traffic-management/_index.md | 9 -
.../tasks/traffic-management/ingress/_index.md | 9 -
.../traffic-management/ingress/gateway-api.md | 68 -------
content/zh-cn/overview/mesh/upgrade/_index.md | 9 -
.../overview/reference/pixiu/install/kubernetes.md | 32 +---
.../pixiu/tasks/quickstart/getting-started.md | 6 -
.../reference/pixiu/tasks/traffic/httpproxy.md | 213 ++-------------------
39 files changed, 26 insertions(+), 1439 deletions(-)
diff --git a/content/en/overview/mesh/_index.md
b/content/en/overview/mesh/_index.md
deleted file mode 100644
index 20a370b15eb..00000000000
--- a/content/en/overview/mesh/_index.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-aliases:
- - /en/overview/mannual/
- - /en/docs3-v2/
- - /en/docs3-v2/
-always_unfold: false
-description: Instructions on how to set up and run Dubbo in Proxyless mode
-linkTitle: Service Mesh
-no_list: true
-title: Dubbo Service Mesh
-type: docs
-weight: 3
----
-> The service mesh is currently in an early experimental stage. Standard
features will be gradually completed and supported.
-
-{{< blocks/section color="white" height="auto">}}
-<div class="td-content list-page">
- <div class="lead"></div>
- <header class="article-meta"></header>
- <div class="row">
- <div class="col-sm col-md-6 mb-4">
- <div class="h-100">
- <h4 class="card-title">
- <a href='{{< relref "./getting-started" >}}'>Getting
started</a>
- </h4>
- <p>Quickly and easily try out Dubbo features.</p>
- </div>
- </div>
- <div class="col-sm col-md-6 mb-4">
- <div class="h-100">
- <h4 class="card-title">
- <a href='{{< relref "./setup/install" >}}'>Installation
guide</a>
- </h4>
- <p>Choose the installation guide that best fits your platform
and needs.</p>
- </div>
- </div>
- <div class="col-sm col-md-6 mb-4">
- <div class="h-100">
- <h4 class="card-title">
- <a href='{{< relref "./upgrade" >}}'>Upgrade Dubbo</a>
- </h4>
- <p>Upgrade, downgrade, and manage Dubbo across multiple
control planes.</p>
- </div>
- </div>
- </div>
- <hr>
-</div>
-{{< /blocks/section >}}
-
diff --git a/content/en/overview/mesh/concepts/_index.md
b/content/en/overview/mesh/concepts/_index.md
deleted file mode 100644
index 555b7c38666..00000000000
--- a/content/en/overview/mesh/concepts/_index.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-description: Core Features
-linkTitle: Core Features
-title: Core Features
-type: docs
-weight: 2
-no_list: true
----
-Gain an in-depth understanding of Dubbo Service Mesh's core capabilities,
helping you systematically understand the structure of its components and the
underlying abstraction mechanisms.
-
-{{< blocks/section color="white" height="auto">}}
-<div class="td-content list-page">
- <div class="lead"></div>
- <header class="article-meta"></header>
- <div class="row">
- <div class="col-sm col-md-6 mb-4">
- <div class="h-100">
- <h4 class="card-title">
- <a href='{{< relref "traffic-management" >}}'>Traffic
Management</a>
- </h4>
- <p>Describes Dubbo's traffic routing and control
capabilities.</p>
- </div>
- </div>
- <div class="col-sm col-md-6 mb-4">
- <div class="h-100">
- <h4 class="card-title">
- <a href='{{< relref "security" >}}'>Security</a>
- </h4>
- <p>Describes Dubbo's authentication and authorization
mechanisms.</p>
- </div>
- </div>
- <div class="col-sm col-md-6 mb-4">
- <div class="h-100">
- <h4 class="card-title">
- <a href='{{< relref "observability" >}}'>Observability</a>
- </h4>
- <p>Describes Dubbo's telemetry and monitoring capabilities.</p>
- </div>
- </div>
- </div>
- <hr>
-</div>
-{{< /blocks/section >}}
-
diff --git a/content/en/overview/mesh/concepts/observability.md
b/content/en/overview/mesh/concepts/observability.md
deleted file mode 100644
index 85a7ff16339..00000000000
--- a/content/en/overview/mesh/concepts/observability.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-description: Describes Dubbo telemetry and monitoring capabilities.
-linkTitle: Observability
-title: Observability
-type: docs
-weight: 3
----
-
-Coming soon.
-
diff --git a/content/en/overview/mesh/concepts/security.md
b/content/en/overview/mesh/concepts/security.md
deleted file mode 100644
index 26c39ed8bcc..00000000000
--- a/content/en/overview/mesh/concepts/security.md
+++ /dev/null
@@ -1,135 +0,0 @@
----
-description: Describes Dubbo authentication capabilities.
-linkTitle: Security
-title: Security
-type: docs
-weight: 2
----
-> The service mesh is currently in an early experimental stage. Standard
features will be gradually completed and supported.
-
-## High-level architecture
-
-The security architecture of Dubbo Service Mesh has two core components:
-
-- **Identity**: every workload has an identity that represents who it is.
-- **Authentication**: authentication policies define how services authenticate
each other.
-
-These components work together to provide security for your service mesh.
-
-## Dubbo identities
-
-In Dubbo Service Mesh, every workload has an identity that represents its
origin. Identities are based on the SPIFFE standard and use SPIFFE URIs of the
form: `spiffe://<trust-domain>/ns/<namespace>/sa/<service-account>`.
-
-### Identity format
-
-A Dubbo identity consists of:
-
-- **Trust Domain**: defines the mesh or organizational boundary, defaulting to
`cluster.local`.
-- **Namespace**: the Kubernetes namespace.
-- **Service Account**: the Kubernetes ServiceAccount.
-
-For example, a workload running with ServiceAccount `bookinfo-productpage` in
the `default` namespace has the identity:
-`spiffe://cluster.local/ns/default/sa/bookinfo-productpage`
-
-### Trust domain aliases
-
-Dubbo Service Mesh supports trust domain aliases, allowing a mesh to trust
workloads from multiple trust domains. This is useful in multi-cluster or
multi-tenant scenarios. Using `TrustDomainAliases` in MeshConfig, the control
plane expands identities across trust domains automatically.
-
-## Identity and certificate management
-
-Dubbo Service Mesh uses the SPIFFE standard to manage workload identities and
certificates. Each workload automatically obtains a SPIFFE identity and can
request an X.509 certificate for mutual TLS authentication.
-
-### Certificate issuance
-
-The Dubbo control plane includes a certificate authority (CA) that issues
certificates for workloads. Workloads communicate with the control plane
through the Dubbo Agent to request certificates and rotate them periodically.
-
-### Certificate storage
-
-Workload certificates are stored in the following locations inside the
container:
-
-- Certificate chain: `./etc/certs/cert-chain.pem` or
`./var/run/secrets/workload-spiffe-uds/credentials/cert-chain.pem`
-- Private key: `./etc/certs/key.pem` or
`./var/run/secrets/workload-spiffe-uds/credentials/key.pem`
-- Root certificate: `./etc/certs/root-cert.pem` or
`./var/run/secrets/workload-spiffe-uds/credentials/root-cert.pem`
-
-Certificates can be delivered to workloads via SDS (Secret Discovery Service)
or mounted files.
-
-## Authentication
-
-Dubbo Service Mesh supports peer authentication (PeerAuthentication) for
service-to-service authentication.
-
-### Mutual TLS authentication
-
-Mutual TLS is the primary mechanism for service-to-service authentication in
Dubbo Service Mesh. It provides:
-
-- **Strong service-to-service authentication**: built-in identity and
credential management.
-- **Secure by default**: service-to-service traffic is encrypted by default.
-- **Automatic key management**: automatic key and certificate rotation.
-- **Transparent encryption**: no changes required to application code.
-
-#### Permissive mode
-
-In permissive mode, a service accepts both plaintext and mTLS traffic. This is
useful for gradually migrating to mTLS while still supporting legacy workloads.
-
-#### Secure naming
-
-Secure naming ensures that only workloads with the correct ServiceAccount can
access a given service. Dubbo uses SPIFFE identities to validate service
identities and guarantee that only authorized services can communicate with
each other.
-
-### Authentication architecture
-
-The authentication architecture in Dubbo Service Mesh consists of:
-
-- **Control plane**: `dubbod` manages authentication policies and certificates.
-- **Data plane**: Dubbo Agent enforces authentication policies and handles TLS
handshakes.
-- **Policy storage**: authentication policies are stored as Kubernetes CRDs.
-
-### Authentication policies
-
-Authentication policies specify authentication requirements at mesh,
namespace, or workload scope. Dubbo supports the PeerAuthentication policy to
define service-to-service authentication requirements.
-
-#### Policy storage
-
-Authentication policies are stored as Kubernetes CRDs in the API server. The
Dubbo control plane watches these resources and pushes policy changes to the
data plane.
-
-#### Selector field
-
-PeerAuthentication policies can use the `selector` field to target specific
workloads. If no selector is specified, the policy applies to the entire
namespace or mesh.
-
-#### Peer authentication
-
-PeerAuthentication policies configure service-to-service authentication. They
support the following mTLS modes:
-
-- **STRICT**: only mTLS traffic is accepted.
-- **PERMISSIVE**: both plaintext and mTLS traffic are accepted.
-- **DISABLE**: mTLS is disabled.
-
-The following example configures a PeerAuthentication policy that enforces
STRICT mTLS for all services in the `default` namespace:
-
-```yaml
-apiVersion: security.dubbo.apache.org/v1
-kind: PeerAuthentication
-metadata:
- name: default
- namespace: default
-spec:
- mtls:
- mode: STRICT
-```
-
-### Updating authentication policies
-
-When you update authentication policies, the Dubbo control plane automatically
pushes the new policies to the data plane. Policy changes take effect
immediately without restarting workloads.
-
-## Learn more
-
-After understanding the basic concepts above, you can:
-
-* Try authentication tasks using security policies.
-* Learn about example security policies that can further harden your mesh.
-* Read the FAQ to troubleshoot issues related to security policies.
-
-## Related content
-
-- [Quickstart](/en/overview/mesh/getting-started/)
-- [Traffic management](/en/overview/mesh/concepts/traffic-management/)
-- [Observability](/en/overview/mesh/concepts/observability/)
-
diff --git a/content/en/overview/mesh/concepts/traffic-management.md
b/content/en/overview/mesh/concepts/traffic-management.md
deleted file mode 100644
index 59e48745e4a..00000000000
--- a/content/en/overview/mesh/concepts/traffic-management.md
+++ /dev/null
@@ -1,149 +0,0 @@
----
-description: Describes Dubbo traffic routing and control capabilities.
-linkTitle: Traffic Management
-title: Traffic Management
-type: docs
-weight: 1
----
-> The service mesh is currently in an early experimental stage. Resource
naming may change.
-
-## Introduction
-
-The traffic management model of Dubbo Service Mesh is aligned with Istio, but
optimized for the Dubbo protocol and sidecarless architecture. The core
components are:
-
-- **ServiceRoute**: defines routing rules and controls how requests are routed
to service instances.
-- **SubsetRule**: defines service subsets and traffic policies, such as load
balancing, connection pools, TLS settings, etc.
-
-By configuring these resources, you can achieve traffic routing, load
balancing, and resilience without modifying application code.
-
-## ServiceRoute
-
-ServiceRoute is the core resource used to define routing rules in Dubbo
Service Mesh, corresponding to Istio's VirtualService. It allows you to
configure how requests are routed to different versions or instances of a
service.
-
-ServiceRoute enables you to:
-- Route traffic to different versions of a service (for example, v1 and v2).
-- Route based on request attributes such as headers and paths.
-- Configure weighted routing for canary and gradual rollouts.
-- Configure timeouts and retries for resilience.
-
-### ServiceRoute example
-
-The following example shows how to configure a ServiceRoute to split traffic:
-
-```yaml
-apiVersion: networking.dubbo.apache.org/v1
-kind: ServiceRoute
-metadata:
- name: provider-weights
- namespace: grpc-app
-spec:
- hosts:
- - provider.grpc-app.svc.cluster.local
- http:
- - route:
- - destination:
- host: provider.grpc-app.svc.cluster.local
- subset: v1
- weight: 10
- - destination:
- host: provider.grpc-app.svc.cluster.local
- subset: v2
- weight: 90
-```
-
-#### hosts field
-
-The `hosts` field specifies the services that the ServiceRoute applies to. You
can use either fully qualified domain names (FQDN) or short names. The control
plane automatically resolves short names to FQDNs.
-
-#### Routing rules
-
-Routing rules define how requests are routed to target services. Each rule can
contain:
-
-- **Match conditions**: based on request attributes such as path or headers.
-- **Destination**: target service host, subset, and port.
-- **Weight**: the proportion of traffic sent to each destination.
-
-#### Routing rule priority
-
-When multiple ServiceRoutes match the same service, the control plane applies
them in creation-time order. More specific match conditions take precedence
over generic ones.
-
-### More about routing rules
-
-ServiceRoute supports more complex routing scenarios, including:
-
-- **Path-based routing**: route traffic to different service versions based on
URL path.
-- **Header-based routing**: make routing decisions based on HTTP headers.
-- **Delegated routing**: compose and reuse routing rules via the `delegate`
field.
-
-## SubsetRule
-
-SubsetRule is the resource used to define service subsets and traffic policies
in Dubbo Service Mesh, corresponding to Istio's DestinationRule. It allows you
to organize service instances into logical subsets and configure traffic
policies for each subset.
-
-### Load balancing options
-
-SubsetRule supports multiple load balancing strategies, configured via
`LocalityLbSetting` in MeshConfig:
-
-- **Locality-based load balancing**: prefer instances in the same region or
zone.
-- **ROUND_ROBIN**: distribute requests sequentially across instances.
-- **LEAST_CONN**: route requests to instances with the fewest active
connections.
-
-### SubsetRule example
-
-The following example shows how to create subsets and configure traffic
policies:
-
-```yaml
-apiVersion: networking.dubbo.apache.org/v1
-kind: SubsetRule
-metadata:
- name: provider-versions
- namespace: grpc-app
-spec:
- host: provider.grpc-app.svc.cluster.local
- subsets:
- - name: v1
- labels:
- version: v1
- - name: v2
- labels:
- version: v2
- trafficPolicy:
- loadBalancer:
- simple: ROUND_ROBIN
- tls:
- mode: ISTIO_MUTUAL
-```
-
-Subsets are selected based on Pod labels. In the example above, Pods with
label `version: v1` are placed into subset `v1`, and Pods with `version: v2`
into subset `v2`.
-
-## Gateway
-
-Gateways provide unified control over ingress and egress traffic in the mesh,
allowing you to specify which traffic is allowed to enter or leave the mesh.
-
-Dubbo mesh gateway is implemented based on Kubernetes Gateway API, using Pixiu
Gateway as the data plane proxy.
-
-### Gateway example
-
-```yaml
-apiVersion: gateway.networking.k8s.io/v1
-kind: Gateway
-metadata:
- name: gateway
- namespace: dubbo-ingress
-spec:
- gatewayClassName: dubbo
- listeners:
- - name: default
- hostname: "*.example.com"
- port: 80
- protocol: HTTP
- allowedRoutes:
- namespaces:
- from: All
-```
-
-## Related content
-
-- [Quickstart](/en/overview/mesh/getting-started/)
-- [Security concepts](/en/overview/mesh/concepts/security/)
-- [Observability](/en/overview/mesh/concepts/observability/)
-
diff --git a/content/en/overview/mesh/getting-started.md
b/content/en/overview/mesh/getting-started.md
deleted file mode 100644
index cae5e444a45..00000000000
--- a/content/en/overview/mesh/getting-started.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-description: Quickly try Dubbo features
-linkTitle: Getting started
-title: Quickstart
-type: docs
-weight: 1
----
-> The service mesh is currently in an early experimental stage. Standard
features will be gradually completed and supported.
-
-Dubbo Service Mesh is a proxyless mesh model developed in 2025. This mode
introduces no extra proxy forwarding overhead, making it suitable for all
performance-sensitive applications and for any deployment environment.
-
-- Each deployed application injects a Dubbo Agent that only provides XDS and
SDS services, enabling direct inter-service communication through the native
gRPC xDS client.
-- All injected agents are based on Kubernetes Gateway API to implement
communication between services and external systems.
-
-## Download Dubbo
-
-Go to the Dubbo release page and download the installer for your OS, or
automatically download the latest version (Linux or macOS):
-
-```bash
-curl -L https://dubbo.apache.org/downloadDubbo | sh -
-```
-
-Change to the Dubbo package directory:
-
-```bash
-cd dubbo-x.xx.x
-```
-
-## Install Dubbo
-
-Install Dubbo with the default profile:
-
-```bash
-dubboctl install -y
-```
-
-Label the namespace to tell Dubbo to automatically inject the Dubbo Agent when
deploying applications:
-
-```bash
-kubectl label namespace default dubbo-injection=enabled
-```
-
-{{< blocks/section color="white" height="auto">}}
-<div class="td-content list-page">
- <div class="lead"></div>
- <header class="article-meta"></header>
-
- <div style="width:100%; text-align:center;">
- <a
- class="btn btn-lg btn-primary"
- href='{{< relref "./setup/install" >}}'
- style="min-width:200px; color: white; display: inline-block;
margin: 0 auto; transform: translateX(-40px);"
- >
- Get started with Proxyless mode
- </a>
- </div>
-</div>
-{{< /blocks/section >}}
-
diff --git a/content/en/overview/mesh/setup/_index.md
b/content/en/overview/mesh/setup/_index.md
deleted file mode 100644
index 1acf1d29d30..00000000000
--- a/content/en/overview/mesh/setup/_index.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-description: Proxyless mode
-linkTitle: Proxyless mode
-title: Proxyless mode
-type: docs
-weight: 3
----
-
-Choose the installation guide that best fits your platform and needs.
-
diff --git a/content/en/overview/mesh/setup/install/_index.md
b/content/en/overview/mesh/setup/install/_index.md
deleted file mode 100644
index a0ac872f18c..00000000000
--- a/content/en/overview/mesh/setup/install/_index.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-description: Choose the installation method that best fits your platform and
needs
-linkTitle: Install
-title: Install
-type: docs
-weight: 1
----
-
-Choose the installation method that best fits your platform and needs.
-
diff --git a/content/en/overview/mesh/setup/install/dubboctl.md
b/content/en/overview/mesh/setup/install/dubboctl.md
deleted file mode 100644
index 300b94732dc..00000000000
--- a/content/en/overview/mesh/setup/install/dubboctl.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-description: Install using Dubboctl
-linkTitle: Dubboctl
-title: dubboctl
-type: docs
-weight: 1
----
-
-This installation guide uses the `dubboctl` command-line tool, which provides
rich customization for the Dubbo control plane and data plane adapters. You can
choose any built-in Dubbo profile and further customize it for your specific
needs.
-
-The `dubboctl` command exposes the full DubboOperator API via command-line
flags. These flags can be set individually or passed via YAML files that
contain DubboOperator custom resources (CRs).
-
-## Prerequisites
-
-Before you begin, check the following prerequisites:
-
-1. [Download the Dubbo release](../../getting-started.md)
-
-## Install Dubbo using a profile
-
-```bash
-dubboctl install -y
-```
-
-This command installs the default profile into your Kubernetes cluster.
-
-You can choose any built-in Dubbo profile:
-
-```bash
-dubboctl install --set profile=demo
-```
-
-You can pass the profile name from the command line to install it into the
cluster.
-
-## Generate manifests before installation
-
-```bash
-dubboctl manifest generate > $HOME/generated-manifest.yaml
-```
-
-## Uninstall
-
-To completely uninstall Dubbo from the cluster, run:
-
-```bash
-dubboctl uninstall --remove -y
-```
-
-This removes all Dubbo resources. Future versions will support specifying a
manifest file.
-
-The `dubbo-system` namespace is not removed by default. If you no longer need
it, remove it with:
-
-```bash
-kubectl delete namespace dubbo-system
-```
-
diff --git a/content/en/overview/mesh/setup/install/helm.md
b/content/en/overview/mesh/setup/install/helm.md
deleted file mode 100644
index 0c3d61378ce..00000000000
--- a/content/en/overview/mesh/setup/install/helm.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-description: Install using Helm
-linkTitle: Helm
-title: Helm
-type: docs
-weight: 2
----
-
-Follow this guide to install and configure the Dubbo mesh using Helm.
-
-## Prerequisites
-
-```bash
-helm repo add dubbo https://charts.dubbo.apache.org
-helm repo update
-```
-
-## Installation steps
-
-1. Install the Dubbo Base chart, which contains cluster-wide custom resource
definitions (CRDs). These must be installed before deploying the Dubbo control
plane:
-
-```bash
-helm install dubbo-base dubbo/base -n dubbo-system --create-namespace
-```
-
-2. Install the Dubbo Discovery chart, which deploys Dubbo control plane
services:
-
-```bash
-helm install dubbod dubbo/dubbod -n dubbo-system --wait
-```
-
-## Uninstall
-
-1. List all Dubbo charts installed in the `dubbo-system` namespace:
-
-```bash
-helm ls -n dubbo-system
-```
-
-2. Delete the Dubbo Base chart:
-
-```bash
-helm delete dubbo-base -n dubbo-system
-```
-
-3. Delete the Dubbo Discovery chart:
-
-```bash
-helm delete dubbod -n dubbo-system
-```
-
-4. Delete the `dubbo-system` namespace:
-
-```bash
-kubectl delete namespace dubbo-system
-```
-
diff --git a/content/en/overview/mesh/setup/install/platform/_index.md
b/content/en/overview/mesh/setup/install/platform/_index.md
deleted file mode 100644
index 56add034953..00000000000
--- a/content/en/overview/mesh/setup/install/platform/_index.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-description: Platform-specific prerequisites before installing Dubbo on
different Kubernetes platforms
-linkTitle: Platform setup
-title: Platform setup
-type: docs
-weight: 3
----
-
-Coming soon.
-
diff --git a/content/en/overview/mesh/tasks/_index.md
b/content/en/overview/mesh/tasks/_index.md
deleted file mode 100644
index bbcf8acc19e..00000000000
--- a/content/en/overview/mesh/tasks/_index.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-description: Tasks
-linkTitle: Tasks
-title: Tasks
-type: docs
-weight: 3
-no_list: true
----
-
-Learn how to use various Dubbo features through hands-on tasks.
-
-{{< blocks/section color="white" height="auto">}}
-<div class="td-content list-page">
- <div class="lead"></div>
- <header class="article-meta"></header>
- <div class="row">
- <div class="col-sm col-md-6 mb-4">
- <div class="h-100">
- <h4 class="card-title">
- <a href='{{< relref "./traffic-management" >}}'>Traffic
management</a>
- </h4>
- <p>Learn how to configure and use traffic management
features.</p>
- </div>
- </div>
- <div class="col-sm col-md-6 mb-4">
- <div class="h-100">
- <h4 class="card-title">
- <a href='{{< relref "./security" >}}'>Security</a>
- </h4>
- <p>Learn how to configure and use security features.</p>
- </div>
- </div>
- <div class="col-sm col-md-6 mb-4">
- <div class="h-100">
- <h4 class="card-title">
- <a href='{{< relref "./observability"
>}}'>Observability</a>
- </h4>
- <p>Learn how to configure and use observability features.</p>
- </div>
- </div>
- </div>
- <hr>
-</div>
-{{< /blocks/section >}}
-
diff --git a/content/en/overview/mesh/tasks/observability/_index.md
b/content/en/overview/mesh/tasks/observability/_index.md
deleted file mode 100644
index c6ff9c44017..00000000000
--- a/content/en/overview/mesh/tasks/observability/_index.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-description: Observability tasks
-linkTitle: Observability
-title: Observability
-type: docs
-weight: 3
----
-
-Learn how to configure and use Dubbo Service Mesh observability features
through hands-on tasks.
-
-> Coming soon
-
diff --git a/content/en/overview/mesh/tasks/security/_index.md
b/content/en/overview/mesh/tasks/security/_index.md
deleted file mode 100644
index 7b44494f9c3..00000000000
--- a/content/en/overview/mesh/tasks/security/_index.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-description: Security tasks
-linkTitle: Security
-title: Security
-type: docs
-weight: 2
----
-
-Learn how to configure and use Dubbo Service Mesh security features through
hands-on tasks.
-
-> Coming soon
-
diff --git a/content/en/overview/mesh/tasks/traffic-management/_index.md
b/content/en/overview/mesh/tasks/traffic-management/_index.md
deleted file mode 100644
index 1d2c335afac..00000000000
--- a/content/en/overview/mesh/tasks/traffic-management/_index.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-description: Traffic management tasks
-linkTitle: Traffic Management
-title: Traffic Management
-type: docs
-weight: 1
----
-
-Learn how to configure and use Dubbo Service Mesh traffic management features
through hands-on tasks.
-
-{{< blocks/section color="white" height="auto">}}
-<div class="td-content list-page">
- <div class="lead"></div>
- <header class="article-meta"></header>
- <div class="row">
- <div class="col-sm col-md-6 mb-4">
- <div class="h-100">
- <h4 class="card-title">
- <a href='{{< relref "./ingress" >}}'>Ingress</a>
- </h4>
- <p>Learn how to configure and manage ingress traffic.</p>
- </div>
- </div>
- </div>
- <hr>
-</div>
-{{< /blocks/section >}}
-
diff --git
a/content/en/overview/mesh/tasks/traffic-management/ingress/_index.md
b/content/en/overview/mesh/tasks/traffic-management/ingress/_index.md
deleted file mode 100644
index 4a94a5d8bb2..00000000000
--- a/content/en/overview/mesh/tasks/traffic-management/ingress/_index.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-description: Ingress traffic management tasks
-linkTitle: Ingress
-title: Ingress
-type: docs
-weight: 1
----
-
-Learn how to configure and manage Dubbo Service Mesh ingress traffic through
hands-on tasks.
-
-{{< blocks/section color="white" height="auto">}}
-<div class="td-content list-page">
- <div class="lead"></div>
- <header class="article-meta"></header>
- <div class="row">
- <div class="col-sm col-md-6 mb-4">
- <div class="h-100">
- <h4 class="card-title">
- <a href='{{< relref "./gateway-api" >}}'>Gateway API</a>
- </h4>
- <p>Learn how to configure ingress traffic using Gateway
API.</p>
- </div>
- </div>
- </div>
- <hr>
-</div>
-{{< /blocks/section >}}
-
diff --git
a/content/en/overview/mesh/tasks/traffic-management/ingress/gateway-api.md
b/content/en/overview/mesh/tasks/traffic-management/ingress/gateway-api.md
deleted file mode 100644
index 2d3908c5d05..00000000000
--- a/content/en/overview/mesh/tasks/traffic-management/ingress/gateway-api.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-description: Learn how to use Kubernetes Gateway API
-linkTitle: Kubernetes Gateway API
-title: Kubernetes Gateway API
-type: docs
-weight: 1
----
-
-## Prerequisites
-
-Gateway API is not installed by default. If Gateway API CRDs do not exist,
install them:
-
-```bash
-kubectl get crd gateways.gateway.networking.k8s.io &> /dev/null || \
- { kubectl kustomize
"github.com/kubernetes-sigs/gateway-api/config/crd?ref=v1.4.0" | kubectl apply
-f -; }
-```
-
-## Configure gateway
-
-```bash
-kubectl create -f
https://raw.githubusercontent.com/istio/istio/release-1.28/samples/httpbin/httpbin.yaml
-```
-
-```bash
-kubectl create namespace dubbo-ingress
-kubectl apply -f - <<EOF
-apiVersion: gateway.networking.k8s.io/v1
-kind: Gateway
-metadata:
- name: gateway
- namespace: dubbo-ingress
-spec:
- gatewayClassName: dubbo
- listeners:
- - name: default
- hostname: "*.example.com"
- port: 80
- protocol: HTTP
- allowedRoutes:
- namespaces:
- from: All
----
-apiVersion: gateway.networking.k8s.io/v1
-kind: HTTPRoute
-metadata:
- name: http
- namespace: default
-spec:
- parentRefs:
- - name: gateway
- namespace: dubbo-ingress
- hostnames: ["httpbin.example.com"]
- rules:
- - matches:
- - path:
- type: PathPrefix
- value: /get
- backendRefs:
- - name: httpbin
- port: 8000
-EOF
-```
-
-## Cleanup
-
-```bash
-kubectl delete -f
https://raw.githubusercontent.com/istio/istio/release-1.28/samples/httpbin/httpbin.yaml
-kubectl delete httproute http
-kubectl delete gateways.gateway.networking.k8s.io gateway -n dubbo-ingress
-kubectl delete ns dubbo-ingress
-```
diff --git a/content/en/overview/mesh/upgrade/_index.md
b/content/en/overview/mesh/upgrade/_index.md
deleted file mode 100644
index 878bb8212f2..00000000000
--- a/content/en/overview/mesh/upgrade/_index.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-description: Upgrade, downgrade, and manage Dubbo across multiple control
planes
-linkTitle: Upgrade
-title: Upgrade
-type: docs
-weight: 4
----
-
-Coming soon.
-
diff --git a/content/en/overview/reference/_index.md
b/content/en/overview/reference/_index.md
index 4ccea3e14aa..d90513f3a76 100755
--- a/content/en/overview/reference/_index.md
+++ b/content/en/overview/reference/_index.md
@@ -6,7 +6,7 @@ linkTitle: Others
no_list: true
title: Others
type: docs
-weight: 7
+weight: 3
---
{{< blocks/section color="white" height="auto">}}
diff --git a/content/zh-cn/overview/mesh/_index.md
b/content/zh-cn/overview/mesh/_index.md
deleted file mode 100755
index f77294d5c8b..00000000000
--- a/content/zh-cn/overview/mesh/_index.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-aliases:
- - /zh/overview/mannual/
- - /zh/docs3-v2/
- - /zh-cn/docs3-v2/
-always_unfold: false
-linkTitle: 服务网格
-no_list: true
-title: Dubbo 服务网格
-type: docs
-weight: 3
----
-> 目前服务网格处于初步实验阶段。后续标准功能将逐步完善和支持。
-
-
-
diff --git a/content/zh-cn/overview/mesh/concepts/_index.md
b/content/zh-cn/overview/mesh/concepts/_index.md
deleted file mode 100644
index a8f4c2a37ac..00000000000
--- a/content/zh-cn/overview/mesh/concepts/_index.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-description: 核心功能
-linkTitle: 核心功能
-title: 核心功能
-type: docs
-weight: 2
-no_list: true
----
-深入了解 Dubbo 服务网格的核心能力，帮助您系统性地理解其各组件结构及背后的抽象机制。
-
-{{< blocks/section color="white" height="auto">}}
-<div class="td-content list-page">
- <div class="lead"></div>
- <header class="article-meta"></header>
- <div class="row">
- <div class="col-sm col-md-6 mb-4">
- <div class="h-100">
- <h4 class="card-title">
- <a href='{{< relref "traffic-management" >}}'>流量管理</a>
- </h4>
- <p>描述 Dubbo 的流量路由与控制功能。</p>
- </div>
- </div>
- <div class="col-sm col-md-6 mb-4">
- <div class="h-100">
- <h4 class="card-title">
- <a href='{{< relref "security" >}}'>安全</a>
- </h4>
- <p>描述 Dubbo 的身份认证和授权机制。</p>
- </div>
- </div>
- <div class="col-sm col-md-6 mb-4">
- <div class="h-100">
- <h4 class="card-title">
- <a href='{{< relref "observability" >}}'>可观测性</a>
- </h4>
- <p>描述 Dubbo 的遥测和监控功能。</p>
- </div>
- </div>
- </div>
- <hr>
-</div>
-{{< /blocks/section >}}
-
diff --git a/content/zh-cn/overview/mesh/concepts/observability.md
b/content/zh-cn/overview/mesh/concepts/observability.md
deleted file mode 100644
index d91d7bfa27b..00000000000
--- a/content/zh-cn/overview/mesh/concepts/observability.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-description: 描述 Dubbo 的遥测和监控功能。
-linkTitle: 可观测性
-title: 可观测性
-type: docs
-weight: 3
----
-敬请期待
\ No newline at end of file
diff --git a/content/zh-cn/overview/mesh/concepts/security.md
b/content/zh-cn/overview/mesh/concepts/security.md
deleted file mode 100644
index b90675ccbb1..00000000000
--- a/content/zh-cn/overview/mesh/concepts/security.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-description: 描述 Dubbo 的认证功能。
-linkTitle: 安全
-title: 安全
-type: docs
-weight: 2
----
-敬请期待
-
-## 相关内容
-
-- [快速入门](/zh-cn/overview/mesh/getting-started/)
-- [流量管理](/zh-cn/overview/mesh/concepts/traffic-management/)
-- [可观测性](/zh-cn/overview/mesh/concepts/observability/)
diff --git a/content/zh-cn/overview/mesh/concepts/traffic-management.md
b/content/zh-cn/overview/mesh/concepts/traffic-management.md
deleted file mode 100644
index 983b1843d9d..00000000000
--- a/content/zh-cn/overview/mesh/concepts/traffic-management.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-description: 描述 Dubbo 的流量路由与控制功能。
-linkTitle: 流量管理
-title: 流量管理
-type: docs
-weight: 1
----
-敬请期待
-
-
-## 相关内容
-
-- [快速入门](/zh-cn/overview/mesh/getting-started/)
-- [安全概念](/zh-cn/overview/mesh/concepts/security/)
-- [可观测性](/zh-cn/overview/mesh/concepts/observability/)
diff --git a/content/zh-cn/overview/mesh/getting-started.md
b/content/zh-cn/overview/mesh/getting-started.md
deleted file mode 100644
index 17cc875eaaf..00000000000
--- a/content/zh-cn/overview/mesh/getting-started.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-description: 快速尝试 Dubbo 控制平面
-linkTitle: 入门介绍
-title: 快速入门
-type: docs
-weight: 1
----
-> 目前服务网格处于初步实验阶段。后续标准功能将逐步完善和支持。
-
-Dubbo 在 2025 年推出 proxyless 模式的 gRPC
服务网格模型，该模型没有额外代理转发开销，适合所有性能敏感的应用，并且适用于所有部署环境。
-
-- 每个已部署的应用都会注入 Dubbo 代理，仅提供 XDS 和 SDS 服务。
-- 所有注入的代理均使用 Kubernetes Gateway API 实现服务与外部系统之间的通信。
-
-转到 Dubbo 发布页面，下载适用于您操作系统的安装文件或自动下载并获取最新版本（Linux 或 macOS）：
-```bash
-curl -L https://dubbo.apache.org/downloadDubbo | sh -
-```
-
-转到 Dubbo 包目录
-```bash
-cd dubbo-x.xx.x
-```
-
-使用 default 配置文件安装 Dubbo
-```bash
-dubboctl install -y
-```
-
-给命名空间添加标签，指示 Dubbo 在部署应用的时候，自动注入
-```bash
-kubectl label namespace default dubbo-injection=enabled
-```
-
-{{< blocks/section color="white" height="auto">}}
-<div class="td-content list-page">
- <div class="lead"></div>
- <header class="article-meta"></header>
-
- <div style="width:100%; text-align:center;">
- <a
- class="btn btn-lg btn-primary"
- href='{{< relref "./setup/install" >}}'
- style="min-width:200px; color: white; display: inline-block;
margin: 0 auto; transform: translateX(-40px);"
- >
- 开始使用 Proxyless 模式
- </a>
- </div>
-</div>
-{{< /blocks/section >}}
-
-
-
diff --git a/content/zh-cn/overview/mesh/setup/install/_index.md
b/content/zh-cn/overview/mesh/setup/install/_index.md
deleted file mode 100644
index f821f0cbc3f..00000000000
--- a/content/zh-cn/overview/mesh/setup/install/_index.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-description: 选择最适合您需求和平台的安装方法
-linkTitle: 安装
-title: 安装
-type: docs
-weight: 3
----
-选择最适合您需求和平台的安装方法。
-
-
diff --git a/content/zh-cn/overview/mesh/setup/install/dubboctl.md
b/content/zh-cn/overview/mesh/setup/install/dubboctl.md
deleted file mode 100644
index c932b1eeabe..00000000000
--- a/content/zh-cn/overview/mesh/setup/install/dubboctl.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-description: 使用 Dubboctl 安装
-linkTitle: Dubboctl
-title: dubboctl
-type: docs
-weight: 1
----
-本安装指南使用命令行工具 dubboctl，它提供丰富的定制 Dubbo 控制平面以及数据平面 adapter。可以选取任意一个 Dubbo
内置的配置档，为您的特定需求进一步定制配置。
-
-dubboctl 命令通过命令行的选项支持完整的 DubboOperator API，这些选项用于单独设置、以及接收包含 DubboOperator
定制资源（CR）的 yaml 文件。
-
-## 先决条件
-开始之前，检查下列先决条件
-1. [下载 Dubbod 发行版](../../getting-started.md)
-
-## 使用配置档安装 Dubbo
-```bash
-dubboctl install -y
-```
-此命令在 Kubernetes 集群上安装 default 配置档。
-
-可以选取任意一个 dubbo 内置的配置档
-```bash
-dubboctl install --set profile=demo
-```
-可以通过在命令行传递配置档名称的方式，安装到集群。
-
-## 安装前生成清单文件
-```bash
-dubboctl manifest generate > $HOME/generated-manifest.yaml
-```
-
-## 卸载
-要从集群中完整卸载 Dubbo，运行下面命令
-```bash
-istioctl uninstall --remove -y
-```
-将移除所有 Dubbo 资源,后续版本将会支持指定文件。
-
-命名空间 dubbo-system 默认不会被移除。如果不再需要用下面命令移除该命名空间
-```bash
-kubectl delete namespace dubbo-system
-```
diff --git a/content/zh-cn/overview/mesh/setup/install/helm.md
b/content/zh-cn/overview/mesh/setup/install/helm.md
deleted file mode 100644
index d934692b43a..00000000000
--- a/content/zh-cn/overview/mesh/setup/install/helm.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-description: 使用 Helm 安装
-linkTitle: Helm
-title: Helm
-type: docs
-weight: 2
----
-请遵循本指南使用 Helm 安装和配置 Dubbo 网格。
-
-
-## 先决条件
-
-```bash
-helm repo add dubbo https://charts.dubbo.apache.org
-helm repo update
-```
-
-## 安装步骤
-
-1. 安装 Dubbo Base Chart，它包含了集群范围的自定义资源定义 (CRD)，这些资源必须在部署 Dubbo 控制平面之前安装：
-```bash
-helm install dubbo-base dubbo/base -n dubbo-system --create-namespace
-```
-
-2. 安装 Dubbo Discovery Chart，它用于部署 dubbo 的服务：
-```bash
-helm install istiod dubbo/dubbod -n dubbo-system --wait
-```
-
-## 卸载
-
-1. 列出在命名空间 dubbo-system 中安装的所有 Dubbo Chart
-```bash
-helm ls -n dubbo-system
-```
-
-2. 删除 Dubbo Base Chart：
-```bash
-helm delete dubbo-base -n dubbo-system
-```
-
-3. 删除 Dubbo Discovery Chart：
-```bash
-helm delete dubbod
-```
-
-4. 删除命名空间 dubbo-system：
-```bash
-kubectl delete namespace dubbo-system
-```
diff --git a/content/zh-cn/overview/mesh/setup/install/platform/_index.md
b/content/zh-cn/overview/mesh/setup/install/platform/_index.md
deleted file mode 100644
index 72f46b449c6..00000000000
--- a/content/zh-cn/overview/mesh/setup/install/platform/_index.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-description: 安装前对不同 Kubernetes 平台的准备工作
-linkTitle: 平台安装
-title: 平台安装
-type: docs
-weight: 3
----
-敬请期待
\ No newline at end of file
diff --git a/content/zh-cn/overview/mesh/tasks/_index.md
b/content/zh-cn/overview/mesh/tasks/_index.md
deleted file mode 100644
index 6d505707dc8..00000000000
--- a/content/zh-cn/overview/mesh/tasks/_index.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-description: 任务
-linkTitle: 任务
-title: 任务
-type: docs
-weight: 4
-no_list: true
----
-通过实践方式学习如何利用 Dubbo 服务网格实现既定的目标行为。
-
-{{< blocks/section color="white" height="auto">}}
-<div class="td-content list-page">
- <div class="lead"></div>
- <header class="article-meta"></header>
- <div class="row">
- <div class="col-sm col-md-6 mb-4">
- <div class="h-100">
- <h4 class="card-title">
- <a href='{{< relref "./traffic-management" >}}'>流量管理</a>
- </h4>
- <p>使用网格的流量路由能力。</p>
- </div>
- </div>
- <div class="col-sm col-md-6 mb-4">
- <div class="h-100">
- <h4 class="card-title">
- <a href='{{< relref "./security" >}}'>安全</a>
- </h4>
- <p>使用网格进行安全防护。</p>
- </div>
- </div>
- <div class="col-sm col-md-6 mb-4">
- <div class="h-100">
- <h4 class="card-title">
- <a href='{{< relref "./observability" >}}'>可观测性</a>
- </h4>
- <p>使用网格采集遥测数据。</p>
- </div>
- </div>
- </div>
- <hr>
-</div>
-{{< /blocks/section >}}
diff --git a/content/zh-cn/overview/mesh/tasks/observability/_index.md
b/content/zh-cn/overview/mesh/tasks/observability/_index.md
deleted file mode 100644
index 3e4054579e0..00000000000
--- a/content/zh-cn/overview/mesh/tasks/observability/_index.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-description: 可观测性任务
-linkTitle: 可观测性
-title: 可观测性
-type: docs
-weight: 3
----
-敬请期待
-
diff --git a/content/zh-cn/overview/mesh/tasks/security/_index.md
b/content/zh-cn/overview/mesh/tasks/security/_index.md
deleted file mode 100644
index 3041655eb76..00000000000
--- a/content/zh-cn/overview/mesh/tasks/security/_index.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-description: 安全任务
-linkTitle: 安全
-title: 安全
-type: docs
-weight: 2
----
-敬请期待
-
diff --git a/content/zh-cn/overview/mesh/tasks/traffic-management/_index.md
b/content/zh-cn/overview/mesh/tasks/traffic-management/_index.md
deleted file mode 100644
index ae9680572c3..00000000000
--- a/content/zh-cn/overview/mesh/tasks/traffic-management/_index.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-description: 流量管理任务
-linkTitle: 流量管理
-title: 流量管理
-type: docs
-weight: 1
----
-通过任务实践学习如何配置和使用 Dubbo 服务网格的流量路由功能。
-
diff --git
a/content/zh-cn/overview/mesh/tasks/traffic-management/ingress/_index.md
b/content/zh-cn/overview/mesh/tasks/traffic-management/ingress/_index.md
deleted file mode 100644
index 5c70a2e87d8..00000000000
--- a/content/zh-cn/overview/mesh/tasks/traffic-management/ingress/_index.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-description: 控制 Dubbo 服务网格的入口流量
-linkTitle: ingress
-title: ingress
-type: docs
-weight: 1
----
-
-
diff --git
a/content/zh-cn/overview/mesh/tasks/traffic-management/ingress/gateway-api.md
b/content/zh-cn/overview/mesh/tasks/traffic-management/ingress/gateway-api.md
deleted file mode 100644
index 2a98e5a71f5..00000000000
---
a/content/zh-cn/overview/mesh/tasks/traffic-management/ingress/gateway-api.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-description: 学习如何使用 Kubernetes Gateway API
-linkTitle: Kubernetes Gateway API
-title: Kubernetes Gateway API
-type: docs
-weight: 1
----
-
-## 先决条件
-默认情况下不会安装 Gateway API。如果 Gateway API CRD 不存在，请安装：
-```bash
-kubectl get crd gateways.gateway.networking.k8s.io &> /dev/null || \
- { kubectl kustomize
"github.com/kubernetes-sigs/gateway-api/config/crd?ref=v1.4.0" | kubectl apply
-f -; }
-```
-
-## 配置网关
-```bash
-kubectl create -f
https://raw.githubusercontent.com/istio/istio/release-1.28/samples/httpbin/httpbin.yaml
-```
-
-```bash
-kubectl create namespace dubbo-ingress
-kubectl apply -f - <<EOF
-apiVersion: gateway.networking.k8s.io/v1
-kind: Gateway
-metadata:
- name: gateway
- namespace: dubbo-ingress
-spec:
- gatewayClassName: dubbo
- listeners:
- - name: default
- hostname: "*.example.com"
- port: 80
- protocol: HTTP
- allowedRoutes:
- namespaces:
- from: All
----
-apiVersion: gateway.networking.k8s.io/v1
-kind: HTTPRoute
-metadata:
- name: http
- namespace: default
-spec:
- parentRefs:
- - name: gateway
- namespace: dubbo-ingress
- hostnames: ["httpbin.example.com"]
- rules:
- - matches:
- - path:
- type: PathPrefix
- value: /get
- backendRefs:
- - name: httpbin
- port: 8000
-EOF
-```
-
-## 清理
-
-```bash
-kubectl delete -f
https://raw.githubusercontent.com/istio/istio/release-1.28/samples/httpbin/httpbin.yaml
-kubectl delete httproute http
-kubectl delete gateways.gateway.networking.k8s.io gateway -n dubbo-ingress
-kubectl delete ns dubbo-ingress
-```
\ No newline at end of file
diff --git a/content/zh-cn/overview/mesh/upgrade/_index.md
b/content/zh-cn/overview/mesh/upgrade/_index.md
deleted file mode 100644
index 4f474c38dfc..00000000000
--- a/content/zh-cn/overview/mesh/upgrade/_index.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-description: 跨多个控制平面升级、降级和管理 Dubbo
-linkTitle: 升级
-title: 升级
-type: docs
-weight: 5
----
-敬请期待
-
diff --git a/content/zh-cn/overview/reference/pixiu/install/kubernetes.md
b/content/zh-cn/overview/reference/pixiu/install/kubernetes.md
index 2bf59c8915c..8d4fd8b8023 100644
--- a/content/zh-cn/overview/reference/pixiu/install/kubernetes.md
+++ b/content/zh-cn/overview/reference/pixiu/install/kubernetes.md
@@ -7,40 +7,20 @@ weight: 2
---
本章节介绍如何在 Kubernetes 集群中安装 Pixiu Gateway。需要注意的是，手动安装方式在配置灵活性方面不如 Helm
安装方式。如果需要对 Pixiu Gateway 的安装过程进行更精细的控制，建议使用 Helm 方式进行部署。
-## 先决条件
-
-
-
## 使用 YAML 安装
```
kubectl apply --server-side -f
https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.3.0/standard-install.yaml
-kubectl apply -f
https://raw.githubusercontent.com/apache/dubbo-go-pixiu/develop/controllers/config/crd/bases
-```
-
-### Pixiu Gateway
-```
-https://raw.githubusercontent.com/apache/dubbo-go-pixiu/develop/controllers/samples/controller.yaml
+kubectl apply -k
https://github.com/apache/dubbo-go-pixiu/controllers/config/crd?ref=develop
```
-### Pixiu Proxy
+## 创建 Pixiu Gateway
```
-https://raw.githubusercontent.com/apache/dubbo-go-pixiu/develop/controllers/samples/pixiugateway.yaml
+kubectl apply -f
https://raw.githubusercontent.com/apache/dubbo-go-pixiu-samples/main/gateway/k8s/pixiu-gateway.yaml
```
```
-NAME READY STATUS RESTARTS AGE
-pg-controller-5999ccd96c-fcrvw 1/1 Running 0 28s
-pixiu-listeners-b6c63d63-68848d4d48-4pt6w 1/1 Running 0 16s
+NAME READY STATUS RESTARTS AGE
+pixiu-3465d618-7456884484-5rzs9 1/1 Running 0 37s
+pixiu-gateway-864764d586-wgvsx 1/1 Running 0 57s
```
-
-### 测试
-```bash
-kubectl apply -f
https://raw.githubusercontent.com/apache/dubbo-go-pixiu/develop/controllers/samples/backend.yaml
-```
-
-```bash
-export GATEWAY_HOST=$(kubectl get gateway/pixiu-listeners -n
pixiu-gateway-system -o jsonpath='{.status.addresses[0].value}')
-curl --verbose --header "Host: www.example.com" http://$GATEWAY_HOST/get
-```
-
diff --git
a/content/zh-cn/overview/reference/pixiu/tasks/quickstart/getting-started.md
b/content/zh-cn/overview/reference/pixiu/tasks/quickstart/getting-started.md
deleted file mode 100644
index 978f4557d54..00000000000
--- a/content/zh-cn/overview/reference/pixiu/tasks/quickstart/getting-started.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-linkTitle: 快速开始
-title: 快速开始
-type: docs
-weight: 1
----
diff --git a/content/zh-cn/overview/reference/pixiu/tasks/traffic/httpproxy.md
b/content/zh-cn/overview/reference/pixiu/tasks/traffic/httpproxy.md
index d05ca2286a5..1bace2d2be8 100644
--- a/content/zh-cn/overview/reference/pixiu/tasks/traffic/httpproxy.md
+++ b/content/zh-cn/overview/reference/pixiu/tasks/traffic/httpproxy.md
@@ -13,95 +13,18 @@ weight: 1
本示例演示了如何使用 Pixiu Gateway 作为 HTTP 代理网关，接收外部的 HTTP 请求并转发到后端的 Dubbo-go RPC
服务。示例基于 `dubbo-go-samples/helloworld` 中的 RPC 服务。
## 先决条件
-- 安装 [Pixiu Gateway](../quickstart/getting-started.md)
+- 已安装 [Pixiu Gateway](../../install/_index.md)
-## 部署后端 RPC 服务
+## 创建 RPC 服务
-### 1. 创建命名空间和服务
+### 创建服务
-首先创建命名空间和后端 RPC 服务：
-```yaml
-cat <<EOF | kubectl apply -f -
-apiVersion: v1
-kind: Namespace
-metadata:
- name: helloworld
----
-apiVersion: v1
-kind: Service
-metadata:
- name: dubbo-go-server
- namespace: helloworld
- labels:
- app: dubbo-go-server
-spec:
- type: ClusterIP
- ports:
- - name: triple
- protocol: TCP
- port: 20000
- targetPort: 20000
- selector:
- app: dubbo-go-server
----
-apiVersion: apps/v1
-kind: Deployment
-metadata:
- name: dubbo-go-server
- namespace: helloworld
- labels:
- app: dubbo-go-server
-spec:
- replicas: 1
- selector:
- matchLabels:
- app: dubbo-go-server
- template:
- metadata:
- labels:
- app: dubbo-go-server
- spec:
- containers:
- - name: server
- image: mfordjody/dubbo-go-server:debug
- imagePullPolicy: Always
- ports:
- - name: triple
- containerPort: 20000
- protocol: TCP
- env:
- - name: DUBBO_GO_CONFIG_PATH
- value: "/app/conf/dubbogo.yml"
- resources:
- limits:
- cpu: 500m
- memory: 512Mi
- requests:
- cpu: 100m
- memory: 128Mi
- livenessProbe:
- tcpSocket:
- port: 20000
- initialDelaySeconds: 30
- periodSeconds: 30
- timeoutSeconds: 5
- failureThreshold: 3
- readinessProbe:
- tcpSocket:
- port: 20000
- initialDelaySeconds: 10
- periodSeconds: 10
- timeoutSeconds: 3
- failureThreshold: 3
-EOF
-```
-
-应用配置：
+首先创建 helloworld 服务：
```bash
-kubectl apply -f helloworld-deployment.yaml
+kubectl apply -f
https://raw.githubusercontent.com/apache/dubbo-go-pixiu-samples/main/gateway/helloworld/deployment.yaml
```
-### 2. 验证
+### 验证服务
检查服务是否正常运行：
```bash
@@ -109,135 +32,37 @@ kubectl get pods -n helloworld
kubectl get svc -n helloworld
```
-## 配置 HTTP 代理
-
-### 1. HTTPRoute
-
-使用 HTTPRoute 定义路由规则，将 HTTP 请求路由到后端服务：
-```yaml
-apiVersion: gateway.networking.k8s.io/v1
-kind: HTTPRoute
-metadata:
- name: helloworld-http-route
- namespace: default
-spec:
- parentRefs:
- - name: pixiu-listeners
- namespace: pixiu-gateway-system
- sectionName: http
- rules:
- - matches:
- - path:
- type: PathPrefix
- value: /greet.GreetService
- backendRefs:
- - name: dubbo-go-server
- namespace: helloworld
- port: 20000
- weight: 100
-```
-
-### 2. PixiuClusterPolicy
-
-配置后端集群策略，定义后端服务的连接信息：
-```yaml
-apiVersion: pixiu.apache.org/v1alpha1
-kind: PixiuClusterPolicy
-metadata:
- name: helloworld-cluster
- namespace: pixiu-gateway-system
-spec:
- targetRef:
- group: gateway.networking.k8s.io
- kind: Gateway
- name: pixiu-listeners
- clusterRef:
- - name: helloworld-dubbo-go-server
- type: static
- loadBalancerPolicy: "lb"
- endpoints:
- - address: dubbo-go-server.helloworld.svc.cluster.local
- port: 20000
-```
-
-### 3. PixiuFilterPolicy
-
-配置 HTTP 过滤器策略，使用 `httpproxy` 过滤器进行代理转发：
-```yaml
-apiVersion: pixiu.apache.org/v1alpha1
-kind: PixiuFilterPolicy
-metadata:
- name: helloworld-http-filter
- namespace: pixiu-gateway-system
-spec:
- targetRef:
- group: gateway.networking.k8s.io
- kind: Gateway
- name: pixiu-listeners
- listenersRef:
- - name: http
- filterChains:
- type: dgp.filter.httpconnectionmanager
- config:
- routeConfig:
- routes:
- - match:
- prefix: "/greet.GreetService"
- methods: []
- route:
- cluster: "helloworld-dubbo-go-server"
- cluster_not_found_response_code: 505
- - match:
- path: "/greet.GreetService/Greet"
- methods: []
- route:
- cluster: "helloworld-dubbo-go-server"
- cluster_not_found_response_code: 505
- httpFilters:
- - name: dgp.filter.http.httpproxy
- config:
- timeoutConfig:
- connectTimeout: 5s
- requestTimeout: 5s
-```
-
-### 4. 应用配置
-
-以上三个配置合并到 `helloworld-http.yaml`
+### 创建 HTTP 代理
```bash
-kubectl apply -f helloworld-http.yaml
+kubectl apply -f
https://raw.githubusercontent.com/apache/dubbo-go-pixiu-samples/main/gateway/http/http.yaml
```
-### 5. 验证
+### 验证 HTTP 代理
检查所有资源的状态：
```bash
kubectl get httproute -n default
-
-kubectl get pixiuclusterpolicy -n pixiu-gateway-system
-
-kubectl get pixiufilterpolicy -n pixiu-gateway-system
-
-kubectl get gateway -n pixiu-gateway-system
+kubectl get pixiuclusterpolicy -n default
+kubectl get pixiufilterpolicy -n default
+kubectl get gateway -n default
```
-## 测试
+## 验证
-### 1. 获取网关地址
+### 获取网关地址
```bash
-kubectl get svc -npixiu-gateway-system
-NAME TYPE CLUSTER-IP EXTERNAL-IP
PORT(S) AGE
-service/pg-controller ClusterIP 10.98.137.160 <none>
8080/TCP,8081/TCP 58s
-service/pixiu-listeners-b6c63d63 LoadBalancer 10.100.42.144 <pending>
80:31257/TCP 24s
+NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S)
AGE
+pixiu-3465d618 LoadBalancer 10.108.197.9 <pending> 80:32547/TCP
86m
+pixiu-gateway ClusterIP 10.105.156.54 <none>
8080/TCP,8081/TCP 86m
```
-### 2. 发送 HTTP 请求
+### 发送 HTTP 请求
使用 curl 发送 HTTP 请求到 RPC 服务：
```bash
NODE_IP=$(kubectl get nodes -o
jsonpath='{.items[0].status.addresses[?(@.type=="InternalIP")].address}')
-curl -v --header "Content-Type: application/json" --data '{"name": "Hello
World"}' http://$NODE_IP:31257/greet.GreetService/Greet
+curl -v --header "Content-Type: application/json" --data '{"name": "Hello
World"}' http://$NODE_IP:32547/greet.GreetService/Greet
```
预期响应：
