This is an automated email from the ASF dual-hosted git repository.
alinsran pushed a commit to branch doc/fix-doc-description-error
in repository https://gitbox.apache.org/repos/asf/apisix-ingress-controller.git
commit 915b4e25fa7b52b6b0459e56e29ce56343ee05f3
Author: Foo Bar <f...@example.com>
AuthorDate: Wed Jul 2 09:01:38 2025 +0800
docs: fix description error in upgrade doc
---
docs/concepts/resources.md | 2 +-
docs/upgrade-guide.md | 18 +++++++++---------
2 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/docs/concepts/resources.md b/docs/concepts/resources.md
index cb42d9fc..8660a7bc 100644
--- a/docs/concepts/resources.md
+++ b/docs/concepts/resources.md
@@ -70,7 +70,7 @@ Enable additional features not included in the standard
Kubernetes Gateway API,
-## Ingress API Extensions
+### Ingress API Extensions
APISIX Ingress Controller CRDs extend Kubernetes functionality to provide
declarative configuration management for the Apache APISIX gateway, supporting
advanced routing, traffic management, and security policies.
diff --git a/docs/upgrade-guide.md b/docs/upgrade-guide.md
index 0a34b956..efbeba4f 100644
--- a/docs/upgrade-guide.md
+++ b/docs/upgrade-guide.md
@@ -64,7 +64,7 @@ etcdserver:
##### Controller-Only Configuration Source
-In 2.0.0, all data plane configurations must originate from the Ingress
Controller. Configurations via Admin API or any external methods are no longer
supported and will be ignored or may cause errors.
+In APISIX Ingress Controller 2.0.0, a full-sync mode is used. All Data Plane
configurations must originate from the Ingress Controller. Any additional route
configurations made via the Admin API or other external methods will be ignored.
### Ingress Configuration Changes
@@ -133,7 +133,7 @@ spec:
#### `ApisixUpstream`
-Due to current limitations in the ADC (API Definition Controller) component,
the following fields are not yet supported:
+Due to current limitations in the [ADC](https://github.com/api7/adc)
component, the following fields are not yet supported:
* `spec.discovery`: Service Discovery
* `spec.healthCheck`: Health Checking
@@ -197,10 +197,10 @@ Ingress annotations used in version 1.x.x are not fully
supported in 2.0.0. If y
### Summary
-| Category | Description
|
-| ---------------- |
----------------------------------------------------------------------------------------------------
|
-| Architecture | The `mock-etcd` component has been removed. Configuration
is now centralized through the Controller. |
-| Configuration | Static configuration fields have been removed. Use
`GatewayProxy` CRD to configure the data plane. |
-| Data Plane | Requires APISIX version 3.13.0 running in `standalone`
mode. |
-| API | Some fields in `Ingress Annotations` and `ApisixUpstream`
are not yet supported. |
-| Upgrade Strategy | Blue-green deployment or canary release is recommended
before full switchover. |
+| Category | Description
|
+| ---------------- |
---------------------------------------------------------------------------------------------------------------------------------
|
+| Architecture | The `mock-etcd` component has been removed. Configuration
is now centralized through the Controller. |
+| Configuration | Static configuration fields have been removed. Use
`GatewayProxy` CRD to configure the data plane. |
+| Data Plane | The Admin API configuration method is still supported,
and support for the Standalone API-driven mode introduced in APISIX 3.13+. |
+| API | Some fields in `Ingress Annotations` and `ApisixUpstream`
are not yet supported. |
+| Upgrade Strategy | Blue-green deployment or canary release is recommended
before full switchover. |
