diff --git a/docs/en/latest/concepts/gateway-api.md b/docs/en/latest/concepts/gateway-api.md
index 44f5376f1..ce431a715 100644
--- a/docs/en/latest/concepts/gateway-api.md
+++ b/docs/en/latest/concepts/gateway-api.md
@@ -9,11 +9,11 @@ keywords:
 <!--
 #
 # Licensed to the Apache Software Foundation (ASF) under one or more
-# contributor license agreements.  See the NOTICE file distributed with
+# contributor license agreements. See the NOTICE file distributed with
 # this work for additional information regarding copyright ownership.
 # The ASF licenses this file to You under the Apache License, Version 2.0
 # (the "License"); you may not use this file except in compliance with
-# the License.  You may obtain a copy of the License at
+# the License. You may obtain a copy of the License at
 #
 #     http://www.apache.org/licenses/LICENSE-2.0
 #
@@ -31,11 +31,15 @@ By supporting Gateway API, the APISIX Ingress controller can realize richer func
 
 ## Concepts
 
-- **GatewayClass**: Defines a set of Gateways that share a common configuration and behavior. Each GatewayClass is handled by a single controller, although controllers may handle more than one GatewayClass.
-- **Gateway**: A resource in Kubernetes that describes how traffic can be translated to services within the cluster.
-- **HTTPRoute**: Can be attached to a Gateway to configure HTTP
-
-For more information about Gateway API, please refer to [Gateway API](https://gateway-api.sigs.k8s.io/).
+- **GatewayClass**: Defines a class of Gateways with a shared configuration and behavior. Each GatewayClass is managed by a single controller, although a controller may support multiple GatewayClasses.
+- **Gateway**: Represents a request for network traffic handling within the cluster. A Gateway specifies how traffic enters the cluster and is directed to backend Services, typically by binding to one or more listeners.
+- **HTTPRoute**: Configures routing for HTTP traffic.
+- **GRPCRoute**: Configures routing for gRPC traffic.
+- **ReferenceGrant**: Grants permission to reference resources across namespaces.
+- **TLSRoute**: Defines routing rules for terminating or passing through TLS traffic.
+- **TCPRoute**: Configures routing for TCP traffic.
+- **UDPRoute**: Configures routing for UDP traffic.
+- **BackendTLSPolicy**: Specifies how a Gateway should validate TLS connections to its backends, including trusted certificate authorities and verification modes.
 
 ## Gateway API Support Level
 
@@ -45,62 +49,38 @@ For more information about Gateway API, please refer to [Gateway API](https://ga
 | Gateway          | Partially supported | Partially supported    | Not supported                         | v1          |
 | HTTPRoute        | Supported           | Partially supported    | Not supported                         | v1          |
 | GRPCRoute        | Not supported       | Not supported          | Not supported                         | v1          |
-| ReferenceGrant   | Not supported       | Not supported          | Not supported                         | v1beta1     |
+| ReferenceGrant   | Supported           | Not supported          | Not supported                         | v1beta1     |
 | TLSRoute         | Not supported       | Not supported          | Not supported                         | v1alpha2    |
 | TCPRoute         | Not supported       | Not supported          | Not supported                         | v1alpha2    |
 | UDPRoute         | Not supported       | Not supported          | Not supported                         | v1alpha2    |
 | BackendTLSPolicy | Not supported       | Not supported          | Not supported                         | v1alpha3    |
 
-## HTTPRoute
+## Examples
 
-The HTTPRoute resource allows users to configure HTTP routing by matching HTTP traffic and forwarding it to Kubernetes backends. Currently, the only backend supported by APISIX Gateway is the Service resource.
+For configuration examples, see the Gateway API tabs in [Configuration Examples](../reference/example.md).
 
-### Example
+For a complete list of configuration options, refer to the [Gateway API Reference](https://gateway-api.sigs.k8s.io/reference/spec/). Be aware that some fields are not supported, or partially supported.
 
-The following example demonstrates how to configure an HTTPRoute resource to route traffic to the `httpbin` service:
+## Unsupported / Partially Supported Fields
 
-```yaml
-apiVersion: gateway.networking.k8s.io/v1
-kind: GatewayClass
-metadata:
-  name: apisix
-spec:
-  controllerName: "apisix.apache.org/apisix-ingress-controller"
+The fields below are specified in the Gateway API specification but are either partially implemented or not yet supported in the APISIX Ingress Controller.
 
----
+### HTTPRoute
 
-apiVersion: gateway.networking.k8s.io/v1
-kind: Gateway
-metadata:
-  name: apisix
-  namespace: default
-spec:
-  gatewayClassName: apisix
-  listeners:
-  - name: http
-    protocol: HTTP
-    port: 80
+| Fields                         | Status                 | Notes                                                                                   |
+|--------------------------------|------------------------|-----------------------------------------------------------------------------------------|
+| `spec.timeouts`                | Not supported          | The field is unsupported because ADC provides finer-grained timeout configuration (connect, read, write), whereas `spec.timeouts` only allows a general total timeout and upstream timeout, so it cannot be directly mapped. To configure route timeouts, you can use [BackendTrafficPolicy](../reference/api-reference.md#backendtrafficpolicyspec).  |
+| `spec.retries`                 | Not supported          | The field is unsupported because APISIX does not support the features in retries. To configure route retries, you can use [BackendTrafficPolicy](../reference/api-reference.md#backendtrafficpolicyspec).  |
+| `spec.sessionPersistence`      | Not supported          | APISIX does not support the configuration of cookie lifetimes. As an alternative, you can use [`chash` load balancer](../reference/api-reference.md#loadbalancer). |
+| `spec.rules[].backendRefs[].filters[]` | Not supported | BackendRef-level filters are not implemented as data plane does not support filtering at this level; only rule-level filters (`spec.rules[].filters[]`) are supported. |
 
----
+### Gateway
 
-apiVersion: gateway.networking.k8s.io/v1
-kind: HTTPRoute
-metadata:
-  name: httpbin
-spec:
-  parentRefs:
-  - name: apisix
-  hostnames:
-  - backends.example
-  rules:
-  - matches: 
-    - path:
-        type: Exact
-        value: /get
-    - path:
-        type: Exact
-        value: /headers
-    backendRefs:
-    - name: httpbin
-      port: 80
-```
+| Fields                                               | Status               | Notes                                                                                          |
+|------------------------------------------------------|----------------------|------------------------------------------------------------------------------------------------|
+| `spec.listeners[].port`               | Not supported*  | The configuration is required but ignored. This is due to limitations in the data plane: it cannot dynamically open new ports. Since the Ingress Controller does not manage the data plane deployment, it cannot automatically update the configuration or restart the data plane to apply port changes.    |
+| `spec.listeners[].allowedRoutes.kinds`               | Partially supported  | Only `HTTPRoute` (group `gateway.networking.k8s.io`) is accepted; other kinds are rejected.    |
+| `spec.listeners[].tls.certificateRefs[].group` | Partially supported | Only `""` is supported; other group values cause validation failure. |
+| `spec.listeners[].tls.certificateRefs[].kind`        | Partially supported  | Only `Secret` is supported.                                                                    |
+| `spec.listeners[].tls.mode`                          | Partially supported  | `Terminate` is implemented; `Passthrough` is effectively unsupported for Gateway listeners.    |
+| `spec.addresses`                                     | Not supported        | Controller does not read or act on `spec.addresses`.                                           |
diff --git a/docs/en/latest/configure.md b/docs/en/latest/configure.md
index c4a104e90..eefc02519 100644
--- a/docs/en/latest/configure.md
+++ b/docs/en/latest/configure.md
@@ -50,6 +50,7 @@ The `controller_name` field is used to identify the `controllerName` in the Gate
 apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
+  namespace: ingress-apisix
   name: apisix
 spec:
   controllerName: "apisix.apache.org/apisix-ingress-controller"
diff --git a/docs/en/latest/getting-started/configure-routes.md b/docs/en/latest/getting-started/configure-routes.md
index e248e981d..c90be316c 100644
--- a/docs/en/latest/getting-started/configure-routes.md
+++ b/docs/en/latest/getting-started/configure-routes.md
@@ -63,6 +63,7 @@ If you are using Gateway API, you should first configure the GatewayClass and Ga
 apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
+  namespace: ingress-apisix
   name: apisix
 spec:
   controllerName: apisix.apache.org/apisix-ingress-controller
@@ -70,6 +71,7 @@ spec:
 apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
+  namespace: ingress-apisix
   name: apisix
 spec:
   gatewayClassName: apisix
@@ -107,6 +109,7 @@ values={[
 apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
+  namespace: ingress-apisix
   name: getting-started-ip
 spec:
   parentRefs:
@@ -129,6 +132,7 @@ spec:
 apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
+  namespace: ingress-apisix
   name: getting-started-ip
 spec:
   ingressClassName: apisix
@@ -152,6 +156,7 @@ spec:
 apiVersion: apisix.apache.org/v2
 kind: ApisixRoute
 metadata:
+  namespace: ingress-apisix
   name: getting-started-ip
 spec:
   ingressClassName: apisix
diff --git a/docs/en/latest/getting-started/key-authentication.md b/docs/en/latest/getting-started/key-authentication.md
index 0c7e38e84..54f8c54ed 100644
--- a/docs/en/latest/getting-started/key-authentication.md
+++ b/docs/en/latest/getting-started/key-authentication.md
@@ -53,6 +53,7 @@ If you are using Gateway API, you should first configure the GatewayClass and Ga
 apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
+  namespace: ingress-apisix
   name: apisix
 spec:
   controllerName: apisix.apache.org/apisix-ingress-controller
@@ -60,6 +61,7 @@ spec:
 apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
+  namespace: ingress-apisix
   name: apisix
 spec:
   gatewayClassName: apisix
@@ -96,6 +98,7 @@ Create a Kubernetes manifest file to configure a consumer:
 apiVersion: apisix.apache.org/v1alpha1
 kind: Consumer
 metadata:
+  namespace: ingress-apisix
   name: tom
 spec:
   gatewayRef:
@@ -113,6 +116,7 @@ Create a Kubernetes manifest file to configure a route and enable key authentica
 apiVersion: v1
 kind: Service
 metadata:
+  namespace: ingress-apisix
   name: httpbin-external-domain
 spec:
   type: ExternalName
@@ -121,6 +125,7 @@ spec:
 apiVersion: apisix.apache.org/v1alpha1
 kind: PluginConfig
 metadata:
+  namespace: ingress-apisix
   name: auth-plugin-config
 spec:
   plugins:
@@ -132,6 +137,7 @@ spec:
 apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
+  namespace: ingress-apisix
   name: getting-started-ip
 spec:
   parentRefs:
@@ -168,6 +174,7 @@ Create a Kubernetes manifest file to configure a consumer:
 apiVersion: apisix.apache.org/v2
 kind: ApisixConsumer
 metadata:
+  namespace: ingress-apisix
   name: tom
 spec:
   ingressClassName: apisix
@@ -183,6 +190,7 @@ Create a Kubernetes manifest file to configure a route and enable key authentica
 apiVersion: apisix.apache.org/v2
 kind: ApisixUpstream
 metadata:
+  namespace: ingress-apisix
   name: httpbin-external-domain
 spec:
   externalNodes:
@@ -192,6 +200,7 @@ spec:
 apiVersion: apisix.apache.org/v2
 kind: ApisixRoute
 metadata:
+  namespace: ingress-apisix
   name: getting-started-ip
 spec:
   ingressClassName: apisix
diff --git a/docs/en/latest/getting-started/load-balancing.md b/docs/en/latest/getting-started/load-balancing.md
index 8eb6b81cd..5a4304110 100644
--- a/docs/en/latest/getting-started/load-balancing.md
+++ b/docs/en/latest/getting-started/load-balancing.md
@@ -53,6 +53,7 @@ If you are using Gateway API, you should first configure the GatewayClass and Ga
 apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
+  namespace: ingress-apisix
   name: apisix
 spec:
   controllerName: apisix.apache.org/apisix-ingress-controller
@@ -60,6 +61,7 @@ spec:
 apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
+  namespace: ingress-apisix
   name: apisix
 spec:
   gatewayClassName: apisix
@@ -96,6 +98,7 @@ values={[
 apiVersion: v1
 kind: Service
 metadata:
+  namespace: ingress-apisix
   name: httpbin-external-domain
 spec:
   type: ExternalName
@@ -104,6 +107,7 @@ spec:
 apiVersion: v1
 kind: Service
 metadata:
+  namespace: ingress-apisix
   name: mockapi7-external-domain
 spec:
   type: ExternalName
@@ -112,6 +116,7 @@ spec:
 apiVersion: apisix.apache.org/v1alpha1
 kind: BackendTrafficPolicy
 metadata:
+  namespace: ingress-apisix
   name: passhost-node
 spec:
   targetRefs:
@@ -127,6 +132,7 @@ spec:
 apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
+  namespace: ingress-apisix
   name: lb-route
 spec:
   parentRefs:
@@ -153,6 +159,7 @@ spec:
 apiVersion: apisix.apache.org/v2
 kind: ApisixUpstream
 metadata:
+  namespace: ingress-apisix
   name: httpbin-external-domain
 spec:
   scheme: https
@@ -166,6 +173,7 @@ spec:
 apiVersion: apisix.apache.org/v2
 kind: ApisixUpstream
 metadata:
+  namespace: ingress-apisix
   name: mockapi7-external-domain
 spec:
   scheme: https
@@ -179,6 +187,7 @@ spec:
 apiVersion: apisix.apache.org/v2
 kind: ApisixRoute
 metadata:
+  namespace: ingress-apisix
   name: lb-route
 spec:
   ingressClassName: apisix
diff --git a/docs/en/latest/getting-started/rate-limiting.md b/docs/en/latest/getting-started/rate-limiting.md
index 82a5f2726..ca852b233 100644
--- a/docs/en/latest/getting-started/rate-limiting.md
+++ b/docs/en/latest/getting-started/rate-limiting.md
@@ -53,6 +53,7 @@ If you are using Gateway API, you should first configure the GatewayClass and Ga
 apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
+  namespace: ingress-apisix
   name: apisix
 spec:
   controllerName: apisix.apache.org/apisix-ingress-controller
@@ -60,6 +61,7 @@ spec:
 apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
+  namespace: ingress-apisix
   name: apisix
 spec:
   gatewayClassName: apisix
@@ -96,6 +98,7 @@ values={[
 apiVersion: v1
 kind: Service
 metadata:
+  namespace: ingress-apisix
   name: httpbin-external-domain
 spec:
   type: ExternalName
@@ -104,6 +107,7 @@ spec:
 apiVersion: apisix.apache.org/v1alpha1
 kind: PluginConfig
 metadata:
+  namespace: ingress-apisix
   name: limit-count-plugin-config
 spec:
   plugins:
@@ -116,6 +120,7 @@ spec:
 apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
+  namespace: ingress-apisix
   name: getting-started-ip
 spec:
   parentRefs:
@@ -144,6 +149,7 @@ spec:
 apiVersion: apisix.apache.org/v2
 kind: ApisixUpstream
 metadata:
+  namespace: ingress-apisix
   name: httpbin-external-domain
 spec:
   externalNodes:
@@ -153,6 +159,7 @@ spec:
 apiVersion: apisix.apache.org/v2
 kind: ApisixRoute
 metadata:
+  namespace: ingress-apisix
   name: getting-started-ip
 spec:
   ingressClassName: apisix
diff --git a/docs/en/latest/reference/example.md b/docs/en/latest/reference/example.md
index 0d326f6c0..cf614ccbf 100644
--- a/docs/en/latest/reference/example.md
+++ b/docs/en/latest/reference/example.md
@@ -19,8 +19,8 @@ To update the Control Plane endpoint and admin key for connectivity between APIS
 apiVersion: apisix.apache.org/v1alpha1
 kind: GatewayProxy
 metadata:
+  namespace: ingress-apisix
   name: apisix-config
-  namespace: apisix-ingress
 spec:
   provider:
     type: ControlPlane
@@ -59,6 +59,7 @@ spec:
 apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
+  namespace: ingress-apisix
   name: apisix
 spec:
   gatewayClassName: apisix
@@ -81,6 +82,7 @@ spec:
 apiVersion: networking.k8s.io/v1
 kind: IngressClass
 metadata:
+  namespace: ingress-apisix
   name: apisix
 spec:
   controller: apisix.apache.org/apisix-ingress-controller
@@ -88,7 +90,7 @@ spec:
     apiGroup: apisix.apache.org
     kind: GatewayProxy
     name: apisix-config
-    namespace: apisix-ingress
+    namespace: ingress-apisix
     scope: Namespace
 ```
 
@@ -107,7 +109,7 @@ spec:
     apiGroup: apisix.apache.org
     kind: GatewayProxy
     name: apisix-config
-    namespace: apisix-ingress
+    namespace: ingress-apisix
     scope: Namespace
 ```
 
@@ -134,6 +136,7 @@ values={[
 apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
+  namespace: ingress-apisix
   name: httpbin
 spec:
   parentRefs:
@@ -156,6 +159,7 @@ spec:
 apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
+  namespace: ingress-apisix
   name: httpbin
 spec:
   ingressClassName: apisix
@@ -179,6 +183,7 @@ spec:
 apiVersion: apisix.apache.org/v2
 kind: ApisixRoute
 metadata:
+  namespace: ingress-apisix
   name: httpbin
 spec:
   ingressClassName: apisix
@@ -215,6 +220,7 @@ values={[
 apiVersion: v1
 kind: Service
 metadata:
+  namespace: ingress-apisix
   name: httpbin-external-domain
 spec:
   type: ExternalName
@@ -223,6 +229,7 @@ spec:
 apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
+  namespace: ingress-apisix
   name: get-ip
 spec:
   parentRefs:
@@ -245,6 +252,7 @@ spec:
 apiVersion: v1
 kind: Service
 metadata:
+  namespace: ingress-apisix
   name: httpbin-external-domain
 spec:
   type: ExternalName
@@ -253,6 +261,7 @@ spec:
 apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
+  namespace: ingress-apisix
   name: get-ip
 spec:
   rules:
@@ -275,6 +284,7 @@ spec:
 apiVersion: apisix.apache.org/v2
 kind: ApisixUpstream
 metadata:
+  namespace: ingress-apisix
   name: httpbin-external-domain
 spec:
   externalNodes:
@@ -284,6 +294,7 @@ spec:
 apiVersion: apisix.apache.org/v2
 kind: ApisixRoute
 metadata:
+  namespace: ingress-apisix
   name: get-ip
 spec:
   ingressClassName: apisix
@@ -318,6 +329,7 @@ values={[
 apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
+  namespace: ingress-apisix
   name: httpbin
 spec:
   parentRefs:
@@ -344,6 +356,7 @@ spec:
 apiVersion: apisix.apache.org/v2
 kind: ApisixRoute
 metadata:
+  namespace: ingress-apisix
   name: httpbin
 spec:
   ingressClassName: apisix
@@ -385,6 +398,7 @@ values={[
 apiVersion: apisix.apache.org/v1alpha1
 kind: BackendTrafficPolicy
 metadata:
+  namespace: ingress-apisix
   name: httpbin
 spec:
   targetRefs:
@@ -411,6 +425,7 @@ spec:
 apiVersion: apisix.apache.org/v2
 kind: ApisixUpstream
 metadata:
+  namespace: ingress-apisix
   name: httpbin
 spec:
   ingressClassName: apisix
@@ -448,6 +463,7 @@ To create a consumer and configure the authentication credentials directly on th
 apiVersion: apisix.apache.org/v1alpha1
 kind: Consumer
 metadata:
+  namespace: ingress-apisix
   name: alice
 spec:
   gatewayRef:
@@ -465,6 +481,7 @@ You can also use the secret CRD, where the credential should be base64 encoded:
 apiVersion: v1
 kind: Secret
 metadata:
+  namespace: ingress-apisix
   name: key-auth-primary
 data:
   key: YWxpY2UtcHJpbWFyeS1rZXk=
@@ -472,6 +489,7 @@ data:
 apiVersion: apisix.apache.org/v1alpha1
 kind: Consumer
 metadata:
+  namespace: ingress-apisix
   name: alice
 spec:
   gatewayRef:
@@ -493,6 +511,7 @@ To create a consumer and configure the authentication credentials directly on th
 apiVersion: apisix.apache.org/v2
 kind: ApisixConsumer
 metadata:
+  namespace: ingress-apisix
   name: alice
 spec:
   ingressClassName: apisix
@@ -508,6 +527,7 @@ You can also use the secret CRD, where the credential should be base64 encoded:
 apiVersion: v1
 kind: Secret
 metadata:
+  namespace: ingress-apisix
   name: key-auth-primary
 data:
   key: YWxpY2UtcHJpbWFyeS1rZXk=
@@ -515,6 +535,7 @@ data:
 apiVersion: apisix.apache.org/v2
 kind: ApisixConsumer
 metadata:
+  namespace: ingress-apisix
   name: alice
 spec:
   ingressClassName: apisix
@@ -546,6 +567,7 @@ values={[
 apiVersion: apisix.apache.org/v1alpha1
 kind: Consumer
 metadata:
+  namespace: ingress-apisix
   name: alice
 spec:
   gatewayRef:
@@ -597,6 +619,7 @@ values={[
 apiVersion: apisix.apache.org/v1alpha1
 kind: HTTPRoutePolicy
 metadata:
+  namespace: ingress-apisix
   name: http-route-policy
 spec:
   targetRefs:
@@ -621,6 +644,7 @@ spec:
 apiVersion: apisix.apache.org/v2
 kind: ApisixRoute
 metadata:
+  namespace: ingress-apisix
   name: httpbin
 spec:
   ingressClassName: apisix
@@ -667,6 +691,7 @@ values={[
 apiVersion: apisix.apache.org/v1alpha1
 kind: PluginConfig
 metadata:
+  namespace: ingress-apisix
   name: auth-plugin-config
 spec:
   plugins:
@@ -678,6 +703,7 @@ spec:
 apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
+  namespace: ingress-apisix
   name: get-ip
 spec:
   parentRefs:
@@ -708,6 +734,7 @@ To enable `basic-auth`, `key-auth`, `wolf-rbac`, `jwt-auth`, `ldap-auth`, or `hm
 apiVersion: apisix.apache.org/v2
 kind: ApisixRoute
 metadata:
+  namespace: ingress-apisix
   name: get-ip
 spec:
   ingressClassName: apisix
@@ -730,6 +757,7 @@ To enable other plugins:
 apiVersion: apisix.apache.org/v2
 kind: ApisixRoute
 metadata:
+  namespace: ingress-apisix
   name: get-ip
 spec:
   ingressClassName: apisix
@@ -772,6 +800,7 @@ values={[
 apiVersion: apisix.apache.org/v1alpha1
 kind: GatewayProxy
 metadata:
+  namespace: ingress-apisix
   name: apisix-config
 spec:
   plugins:
@@ -792,6 +821,7 @@ spec:
 apiVersion: apisix.apache.org/v2
 kind: ApisixGlobalRule
 metadata:
+  namespace: ingress-apisix
   name: apisix-global-rule-logging
 spec:
   ingressClassName: apisix
@@ -828,6 +858,7 @@ values={[
 apiVersion: apisix.apache.org/v1alpha1
 kind: GatewayProxy
 metadata:
+  namespace: ingress-apisix
   name: apisix-config
 spec:
   pluginMetadata:
@@ -882,6 +913,7 @@ values={[
 apiVersion: apisix.apache.org/v1alpha1
 kind: PluginConfig
 metadata:
+  namespace: ingress-apisix
   name: example-plugin-config
 spec:
   plugins:
@@ -895,6 +927,7 @@ spec:
 apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
+  namespace: ingress-apisix
   name: httpbin
 spec:
   parentRefs:
@@ -923,6 +956,7 @@ spec:
 apiVersion: apisix.apache.org/v2
 kind: ApisixPluginConfig
 metadata:
+  namespace: ingress-apisix
   name: example-plugin-config
 spec:
   ingressClassName: apisix
@@ -937,6 +971,7 @@ spec:
 apiVersion: apisix.apache.org/v2
 kind: ApisixRoute
 metadata:
+  namespace: ingress-apisix
   name: httpbin
 spec:
   ingressClassName: apisix
@@ -976,6 +1011,7 @@ To configure the `statusAddress`:
 apiVersion: apisix.apache.org/v1alpha1
 kind: GatewayProxy
 metadata:
+  namespace: ingress-apisix
   name: apisix-config
 spec:
   statusAddress:
@@ -994,6 +1030,7 @@ To configure the `statusAddress`:
 apiVersion: apisix.apache.org/v1alpha1
 kind: GatewayProxy
 metadata:
+  namespace: ingress-apisix
   name: apisix-config
 spec:
   statusAddress:
@@ -1006,6 +1043,7 @@ To configure the `publishService`:
 apiVersion: apisix.apache.org/v1alpha1
 kind: GatewayProxy
 metadata:
+  namespace: ingress-apisix
   name: apisix-config
 spec:
   publishService: apisix-ee-3-gateway-gateway
diff --git a/docs/en/latest/upgrade-guide.md b/docs/en/latest/upgrade-guide.md
index e892e7897..eac2ebf6e 100644
--- a/docs/en/latest/upgrade-guide.md
+++ b/docs/en/latest/upgrade-guide.md
@@ -108,6 +108,7 @@ From version 2.0.0, the data plane must be connected via the `GatewayProxy` CRD:
 apiVersion: networking.k8s.io/v1
 kind: IngressClass
 metadata:
+  namespace: ingress-apisix
   name: apisix
 spec:
   controller: "apisix.apache.org/apisix-ingress-controller"
@@ -121,8 +122,8 @@ spec:
 apiVersion: apisix.apache.org/v1alpha1
 kind: GatewayProxy
 metadata:
+  namespace: ingress-apisix
   name: apisix-proxy-config
-  namespace: default
 spec:
   provider:
     type: ControlPlane