This is an automated email from the ASF dual-hosted git repository.
juzhiyuan pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix-ingress-controller.git
The following commit(s) were added to refs/heads/master by this push:
new 0d8e880d docs: update ingress annotation docs (#2645)
0d8e880d is described below
commit 0d8e880d8660deb29f9f28149804daeb23c5cff1
Author: Traky Deng <[email protected]>
AuthorDate: Thu Nov 13 06:09:33 2025 +0800
docs: update ingress annotation docs (#2645)
---
docs/en/latest/config.json | 3 +-
docs/en/latest/reference/ingress-annotation.md | 612 +++++++++++++++++++++++++
docs/en/latest/upgrade-guide.md | 45 --
3 files changed, 614 insertions(+), 46 deletions(-)
diff --git a/docs/en/latest/config.json b/docs/en/latest/config.json
index 92045e80..7c0c2f66 100644
--- a/docs/en/latest/config.json
+++ b/docs/en/latest/config.json
@@ -39,7 +39,8 @@
"items": [
"reference/api-reference",
"reference/example",
- "reference/configuration-file"
+ "reference/configuration-file",
+ "reference/ingress-annotation"
]
},
{
diff --git a/docs/en/latest/reference/ingress-annotation.md
b/docs/en/latest/reference/ingress-annotation.md
new file mode 100644
index 00000000..bb68422a
--- /dev/null
+++ b/docs/en/latest/reference/ingress-annotation.md
@@ -0,0 +1,612 @@
+---
+title: Ingress Annotations
+slug: /reference/apisix-ingress-controller/annotation
+description: Learn how annotations extend the functionality of Kubernetes
Ingress resource in APISIX Ingress Controller to configure routing, security,
and gateway behaviors.
+---
+
+Annotations are key-value pairs that allow controllers to configure
functionalities that are not available through standard Kubernetes resource
fields. In APISIX Ingress Controller, annotations are commonly used with
Ingress resources to configure gateway behaviors, routing rules, upstream
settings, plugins, and other features. Alternatively, you can use APISIX CRDs
to configure these features for a better experience.
+
+This document describes all available annotations and their uses.
+
+## All Annotations
+
+| Annotation |
+| ------------------------------------------------------ |
+| `kubernetes.io/ingress.class` |
+| `k8s.apisix.apache.org/use-regex` |
+| `k8s.apisix.apache.org/enable-websocket` |
+| `k8s.apisix.apache.org/plugin-config-name` |
+| `k8s.apisix.apache.org/upstream-scheme` |
+| `k8s.apisix.apache.org/upstream-retries` |
+| `k8s.apisix.apache.org/upstream-connect-timeout` |
+| `k8s.apisix.apache.org/upstream-read-timeout` |
+| `k8s.apisix.apache.org/upstream-send-timeout` |
+| `k8s.apisix.apache.org/enable-cors` |
+| `k8s.apisix.apache.org/cors-allow-origin` |
+| `k8s.apisix.apache.org/cors-allow-headers` |
+| `k8s.apisix.apache.org/cors-allow-methods` |
+| `k8s.apisix.apache.org/enable-csrf` |
+| `k8s.apisix.apache.org/csrf-key` |
+| `k8s.apisix.apache.org/http-to-https` |
+| `k8s.apisix.apache.org/http-redirect` |
+| `k8s.apisix.apache.org/http-redirect-code` |
+| `k8s.apisix.apache.org/rewrite-target` |
+| `k8s.apisix.apache.org/rewrite-target-regex` |
+| `k8s.apisix.apache.org/rewrite-target-regex-template` |
+| `k8s.apisix.apache.org/enable-response-rewrite` |
+| `k8s.apisix.apache.org/response-rewrite-status-code` |
+| `k8s.apisix.apache.org/response-rewrite-body` |
+| `k8s.apisix.apache.org/response-rewrite-body-base64` |
+| `k8s.apisix.apache.org/response-rewrite-add-header` |
+| `k8s.apisix.apache.org/response-rewrite-set-header` |
+| `k8s.apisix.apache.org/response-rewrite-remove-header` |
+| `k8s.apisix.apache.org/auth-uri` |
+| `k8s.apisix.apache.org/auth-ssl-verify` |
+| `k8s.apisix.apache.org/auth-request-headers` |
+| `k8s.apisix.apache.org/auth-upstream-headers` |
+| `k8s.apisix.apache.org/auth-client-headers` |
+| `k8s.apisix.apache.org/allowlist-source-range` |
+| `k8s.apisix.apache.org/blocklist-source-range` |
+| `k8s.apisix.apache.org/http-allow-methods` |
+| `k8s.apisix.apache.org/http-block-methods` |
+| `k8s.apisix.apache.org/auth-type` |
+| `k8s.apisix.apache.org/svc-namespace` |
+
+## Annotation Details
+
+Note that annotation keys and values can only be strings.
+
+### Ingress Class
+
+The `kubernetes.io/ingress.class` annotation specifies which ingress
controller should process a given Ingress resource. This is useful when
multiple ingress controllers are deployed in the same cluster.
+
+For example:
+
+```yaml
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+ name: httpbin
+ annotations:
+ kubernetes.io/ingress.class: "apisix"
+spec:
+ rules:
+ - http:
+ paths:
+ - path: /
+ pathType: Prefix
+ backend:
+ service:
+ name: httpbin
+ port:
+ number: 80
+```
+
+### Response Rewrite
+
+These annotations enable you to modify the response returned from the upstream
service before it is sent to the client. They correspond to the functionality
of the `response-rewrite` plugin in APISIX.
+
+| Annotation | Description |
+|-------------|-------------|
+| `k8s.apisix.apache.org/enable-response-rewrite` | Enables the response
rewrite feature. Set to `true` to enable response rewriting for this resource. |
+| `k8s.apisix.apache.org/response-rewrite-status-code` | Specifies a new HTTP
status code for the response. |
+| `k8s.apisix.apache.org/response-rewrite-body` | Replaces the response body
with the specified plain text content. |
+| `k8s.apisix.apache.org/response-rewrite-body-base64` | Replaces the response
body with Base64-encoded content. |
+| `k8s.apisix.apache.org/response-rewrite-add-header` | Adds new headers to
the response. You can specify multiple headers as a comma-separated list. |
+| `k8s.apisix.apache.org/response-rewrite-set-header` | Sets or overrides
existing headers in the response. You can specify multiple headers as a
comma-separated list. |
+| `k8s.apisix.apache.org/response-rewrite-remove-header` | Removes specified
headers from the response. You can specify multiple headers as a
comma-separated list. |
+
+For example:
+
+```yaml
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+ name: httpbin-response-rewrite
+ annotations:
+ # highlight-start
+ k8s.apisix.apache.org/enable-response-rewrite: "true"
+ k8s.apisix.apache.org/response-rewrite-status-code: "403"
+ k8s.apisix.apache.org/response-rewrite-body: "Access denied"
+ k8s.apisix.apache.org/response-rewrite-add-header:
"X-Reason:Forbidden,X-Env:Test"
+ k8s.apisix.apache.org/response-rewrite-remove-header: "header1,header2"
+ # highlight-end
+spec:
+ ingressClassName: apisix
+ rules:
+ - http:
+ paths:
+ - path: /
+ pathType: Prefix
+ backend:
+ service:
+ name: httpbin
+ port:
+ number: 80
+```
+
+### IP Restriction
+
+These annotations control client access based on IP address ranges. They
correspond to the functionality of the `ip-restriction` plugin in APISIX.
+
+| Annotation | Description |
+|-------------|-------------|
+| `k8s.apisix.apache.org/allowlist-source-range` | Comma-separated list of
CIDR ranges that are allowed to access the resource. All other IPs are denied. |
+| `k8s.apisix.apache.org/blocklist-source-range` | Comma-separated list of
CIDR ranges that are blocked from accessing the resource. |
+
+For example:
+
+```yaml
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+ name: example-ip-restriction
+ annotations:
+ k8s.apisix.apache.org/allowlist-source-range: "10.0.0.0/24,192.168.1.0/24"
+spec:
+ ingressClassName: apisix
+ rules:
+ - http:
+ paths:
+ - path: /
+ pathType: Prefix
+ backend:
+ service:
+ name: httpbin
+ port:
+ number: 80
+```
+
+### Forward Auth
+
+These annotations configure an external authentication endpoint that validates
incoming requests before they reach the backend service. They correspond to the
functionality of the `forward-auth` plugin in APISIX.
+
+| Annotation | Description |
+|-------------|-------------|
+| `k8s.apisix.apache.org/auth-uri` | The URI of the external authentication
server. Requests are forwarded to this URI for verification. |
+| `k8s.apisix.apache.org/auth-ssl-verify` | Enables or disables SSL
certificate verification when communicating with the authentication server. Set
to `true` or `false`. |
+| `k8s.apisix.apache.org/auth-request-headers` | Comma-separated list of
request headers to forward to the authentication server. |
+| `k8s.apisix.apache.org/auth-upstream-headers` | Comma-separated list of
headers from the auth response to forward to the upstream service. |
+| `k8s.apisix.apache.org/auth-client-headers` | Comma-separated list of
headers from the auth response to return to the client. |
+
+For example:
+
+```yaml
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+ name: example-forward-auth
+ annotations:
+ k8s.apisix.apache.org/auth-uri: "https://auth.example.com/verify";
+ k8s.apisix.apache.org/auth-ssl-verify: "true"
+ k8s.apisix.apache.org/auth-request-headers: "Authorization"
+ k8s.apisix.apache.org/auth-upstream-headers: "X-User-ID,X-User-Role"
+ k8s.apisix.apache.org/auth-client-headers: "X-Auth-Status"
+spec:
+ ingressClassName: apisix
+ rules:
+ - http:
+ paths:
+ - path: /
+ pathType: Prefix
+ backend:
+ service:
+ name: httpbin
+ port:
+ number: 80
+```
+
+### RegEx Route Matching
+
+The `k8s.apisix.apache.org/use-regex` annotation allows an Ingress to define
routes using regular expressions for advanced path matching. Set to `true` to
interpret the `path` field as a RegEx pattern.
+
+For example:
+
+```yaml
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+ name: example-regex
+ annotations:
+ k8s.apisix.apache.org/use-regex: "true"
+spec:
+ ingressClassName: apisix
+ rules:
+ - http:
+ paths:
+ - path: "/users/[0-9]+"
+ pathType: ImplementationSpecific # should use ImplementationSpecific
with use-regex
+ backend:
+ service:
+ name: user-service
+ port:
+ number: 80
+```
+
+### Authentication
+
+The `k8s.apisix.apache.org/auth-type` annotation specifies the type of
authentication to apply to an Ingress resource. Support `keyAuth` and
`basicAuth`.
+
+For example:
+
+```yaml
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+ name: example-key-auth
+ annotations:
+ k8s.apisix.apache.org/auth-type: "keyAuth"
+spec:
+ ingressClassName: apisix
+ rules:
+ - http:
+ paths:
+ - path: /
+ pathType: Prefix
+ backend:
+ service:
+ name: httpbin
+ port:
+ number: 80
+---
+apiVersion: apisix.apache.org/v2
+kind: ApisixConsumer
+metadata:
+ name: john
+spec:
+ ingressClassName: apisix
+ authParameter:
+ keyAuth:
+ value:
+ key: john-key
+```
+
+### Cross Namespace Service Access
+
+The `k8s.apisix.apache.org/svc-namespace` annotation allows an Ingress to
route traffic to a service located in a different namespace from the Ingress
resource. By default, Ingresses can only reference Services within the same
namespace.
+
+For example:
+
+```yaml
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+ name: cross-namespace-ingress
+ annotations:
+ k8s.apisix.apache.org/svc-namespace: "other-namespace"
+spec:
+ ingressClassName: apisix
+ rules:
+ - http:
+ paths:
+ - path: /
+ pathType: Prefix
+ backend:
+ service:
+ name: backend-service
+ port:
+ number: 80
+```
+
+### Proxy Rewrite
+
+These annotations allow you to rewrite request paths before forwarding them to
the upstream service. They correspond to the functionality of the
`proxy-rewrite` plugin in APISIX.
+
+| Annotation | Description |
+|------------|-------------|
+| `k8s.apisix.apache.org/rewrite-target` | Rewrites the request path to the
specified target path. |
+| `k8s.apisix.apache.org/rewrite-target-regex` | Specifies a regular
expression pattern to match in the original request path. |
+| `k8s.apisix.apache.org/rewrite-target-regex-template` | Template for
rewriting the request path when using `rewrite-target-regex`. Supports
capturing groups from the RegEx pattern. |
+
+For example, the following configuration rewrites requests so that requests to
`/api` are forwarded to `/new-path`:
+
+```yaml
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+ name: example-rewrite
+ annotations:
+ k8s.apisix.apache.org/rewrite-target: "/new-path"
+spec:
+ ingressClassName: apisix
+ rules:
+ - http:
+ paths:
+ - path: /api
+ pathType: Prefix
+ backend:
+ service:
+ name: httpbin
+ port:
+ number: 80
+```
+
+For example, the following configuration rewrites requests so that requests to
`/api/test` are forwarded to `/backend/test`:
+
+```yaml
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+ name: example-regex-rewrite
+ annotations:
+ k8s.apisix.apache.org/rewrite-target-regex: "^/api/(.*)"
+ k8s.apisix.apache.org/rewrite-target-regex-template: "/backend/$1"
+spec:
+ ingressClassName: apisix
+ rules:
+ - http:
+ paths:
+ - path: /api
+ pathType: Prefix
+ backend:
+ service:
+ name: httpbin
+ port:
+ number: 80
+```
+
+### Plugin Config
+
+The `k8s.apisix.apache.org/plugin-config-name` annotation allows you to attach
a predefined APISIX plugin configuration to an Ingress resource. It corresponds
to a PluginConfig resource in APISIX, enabling reusable plugin settings across
multiple routes or services.
+
+For example:
+
+```yaml
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+ name: example-plugin-config
+ annotations:
+ k8s.apisix.apache.org/plugin-config-name: "rate-limit-config"
+spec:
+ ingressClassName: apisix
+ rules:
+ - http:
+ paths:
+ - path: /
+ pathType: Prefix
+ backend:
+ service:
+ name: httpbin
+ port:
+ number: 80
+---
+apiVersion: apisix.apache.org/v2
+kind: ApisixPluginConfig
+metadata:
+ name: rate-limit-config
+spec:
+ ingressClassName: apisix
+ plugins:
+ - name: limit-count
+ enable: true
+ config:
+ count: 2
+ time_window: 10
+ rejected_code: 429
+```
+
+### CSRF
+
+These annotations enable CSRF (Cross-Site Request Forgery) protection for an
Ingress. They correspond to the `csrf` plugin in APISIX.
+
+| Annotation | Description |
+|------------|-------------|
+| `k8s.apisix.apache.org/enable-csrf` | Enables or disables CSRF protection.
Set to `true` to enable the plugin. |
+| `k8s.apisix.apache.org/csrf-key` | Specifies the secret key used to sign and
validate CSRF tokens. |
+
+For example:
+
+```yaml
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+ name: example-csrf
+ annotations:
+ k8s.apisix.apache.org/enable-csrf: "true"
+ k8s.apisix.apache.org/csrf-key: "my-secret-csrf-key"
+spec:
+ ingressClassName: apisix
+ rules:
+ - http:
+ paths:
+ - path: /
+ pathType: Prefix
+ backend:
+ service:
+ name: httpbin
+ port:
+ number: 80
+```
+
+### Allow/Block HTTP Methods
+
+These annotations control which HTTP methods are allowed or blocked for an
Ingress. If both allow and block methods are specified, only the allow list is
effective.
+
+| Annotation | Description |
+|------------|-------------|
+| `k8s.apisix.apache.org/http-allow-methods` | Comma-separated list of HTTP
methods that are explicitly allowed. Requests using other methods will be
denied. |
+| `k8s.apisix.apache.org/http-block-methods` | Comma-separated list of HTTP
methods that are explicitly blocked. Requests using these methods will be
denied. |
+
+For example:
+
+```yaml
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+ name: example-http-methods
+ annotations:
+ k8s.apisix.apache.org/http-allow-methods: "GET,POST"
+spec:
+ ingressClassName: apisix
+ rules:
+ - http:
+ paths:
+ - path: /
+ pathType: Prefix
+ backend:
+ service:
+ name: httpbin
+ port:
+ number: 80
+```
+
+### Enable Websocket
+
+The `k8s.apisix.apache.org/enable-websocket` annotation enables WebSocket
support for an Ingress when set to `true`.
+
+For example:
+
+```yaml
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+ name: example-websocket
+ annotations:
+ k8s.apisix.apache.org/enable-websocket: "true"
+spec:
+ ingressClassName: apisix
+ rules:
+ - http:
+ paths:
+ - path: /ws
+ pathType: Exact
+ backend:
+ service:
+ name: websocket-service
+ port:
+ number: 8080
+```
+
+### Redirect
+
+These annotations configure HTTP-to-HTTPS redirection or custom HTTP redirects
for an Ingress. They correspond to the `redirect` plugin in APISIX.
+
+| Annotation | Description |
+|------------|-------------|
+| `k8s.apisix.apache.org/http-to-https` | Set to `true` to automatically
redirect HTTP requests to HTTPS. |
+| `k8s.apisix.apache.org/http-redirect` | Specifies a custom URL to redirect
requests to. |
+| `k8s.apisix.apache.org/http-redirect-code` | HTTP status code to use for the
redirect. |
+
+For example, the following configuration redirects HTTP requests to HTTPS with
a 301 status code:
+
+```yaml
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+ name: example-https-redirect
+ annotations:
+ k8s.apisix.apache.org/http-to-https: "true"
+spec:
+ ingressClassName: apisix
+ rules:
+ - http:
+ paths:
+ - path: /
+ pathType: Prefix
+ backend:
+ service:
+ name: httpbin
+ port:
+ number: 80
+```
+
+For example, the following configuration redirects HTTP requests to a new URI
with a custom HTTP redirect status code:
+
+```yaml
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+ name: example-custom-redirect
+ annotations:
+ k8s.apisix.apache.org/http-redirect: "https://example.com/new-path";
+ k8s.apisix.apache.org/http-redirect-code: "302"
+spec:
+ ingressClassName: apisix
+ rules:
+ - http:
+ paths:
+ - path: /
+ pathType: Prefix
+ backend:
+ service:
+ name: httpbin
+ port:
+ number: 80
+```
+
+### CORS
+
+These annotations configure Cross-Origin Resource Sharing (CORS) for an
Ingress. They correspond to the `cors` plugin in APISIX.
+
+| Annotation | Description |
+|------------|-------------|
+| `k8s.apisix.apache.org/enable-cors` | Set to `true` to enable CORS. |
+| `k8s.apisix.apache.org/cors-allow-origin` | Specifies the allowed origin(s),
such as `*` or `https://example.com`. |
+| `k8s.apisix.apache.org/cors-allow-headers` | Comma-separated list of allowed
headers in cross-origin requests. |
+| `k8s.apisix.apache.org/cors-allow-methods` | Comma-separated list of allowed
HTTP methods. |
+
+For example:
+
+```yaml
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+ name: example-cors
+ annotations:
+ k8s.apisix.apache.org/enable-cors: "true"
+ k8s.apisix.apache.org/cors-allow-origin: "https://example.com";
+ k8s.apisix.apache.org/cors-allow-headers: "Content-Type,Authorization"
+ k8s.apisix.apache.org/cors-allow-methods: "GET,POST,PUT"
+spec:
+ ingressClassName: apisix
+ rules:
+ - http:
+ paths:
+ - path: /
+ pathType: Prefix
+ backend:
+ service:
+ name: httpbin
+ port:
+ number: 80
+```
+
+### Upstream
+
+These annotations allow you to configure upstream behavior for an Ingress in
APISIX, including scheme, retries, and timeouts. They correspond to the
upstream settings in Apache APISIX.
+
+| Annotation | Description |
+|------------|-------------|
+| `k8s.apisix.apache.org/upstream-scheme` | Specifies the protocol used to
communicate with the upstream service. Default is `http`. Support `http`,
`https`, `grpc`, and `grpcs`. |
+| `k8s.apisix.apache.org/upstream-retries` | Number of retries for upstream
requests in case of failure. |
+| `k8s.apisix.apache.org/upstream-connect-timeout` | Timeout for establishing
a connection to the upstream service. Default is `60s`. |
+| `k8s.apisix.apache.org/upstream-read-timeout` | Timeout for reading a
response from the upstream service. Default is `60s`. |
+| `k8s.apisix.apache.org/upstream-send-timeout` | Timeout for sending a
request to the upstream service. Default is `60s`. |
+
+For example:
+
+```yaml
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+ name: example-upstream
+ annotations:
+ k8s.apisix.apache.org/upstream-scheme: "https"
+ k8s.apisix.apache.org/upstream-retries: "3"
+ k8s.apisix.apache.org/upstream-connect-timeout: "5s"
+ k8s.apisix.apache.org/upstream-read-timeout: "5s"
+ k8s.apisix.apache.org/upstream-send-timeout: "5s"
+spec:
+ ingressClassName: apisix
+ rules:
+ - http:
+ paths:
+ - path: /
+ pathType: Prefix
+ backend:
+ service:
+ name: httpbin
+ port:
+ number: 80
+```
diff --git a/docs/en/latest/upgrade-guide.md b/docs/en/latest/upgrade-guide.md
index 1c3cb200..6495a9f5 100644
--- a/docs/en/latest/upgrade-guide.md
+++ b/docs/en/latest/upgrade-guide.md
@@ -152,51 +152,6 @@ In apisix >= 3.11, most of the hmac-auth related
configuration has been deprecat
Currently supports networking.k8s.io/v1 only. Support for other Ingress API
versions (networking.k8s.io/v1beta1 and extensions/v1beta1) is not yet
available in 2.0.0.
-##### Limited Support for Ingress Annotations
-
-The following Ingress annotations supported in version 1.x.x are not supported
in the current version (2.0.0-rc*). They will be supported in the 2.0.0 final
release. If your existing setup relies on any of the following annotations,
validate compatibility or consider delaying the upgrade.
-
-| Ingress Annotations |
-| ------------------------------------------------------ |
-| `k8s.apisix.apache.org/use-regex` |
-| `k8s.apisix.apache.org/enable-websocket` |
-| `k8s.apisix.apache.org/plugin-config-name` |
-| `k8s.apisix.apache.org/upstream-scheme` |
-| `k8s.apisix.apache.org/upstream-retries` |
-| `k8s.apisix.apache.org/upstream-connect-timeout` |
-| `k8s.apisix.apache.org/upstream-read-timeout` |
-| `k8s.apisix.apache.org/upstream-send-timeout` |
-| `k8s.apisix.apache.org/enable-cors` |
-| `k8s.apisix.apache.org/cors-allow-origin` |
-| `k8s.apisix.apache.org/cors-allow-headers` |
-| `k8s.apisix.apache.org/cors-allow-methods` |
-| `k8s.apisix.apache.org/enable-csrf` |
-| `k8s.apisix.apache.org/csrf-key` |
-| `k8s.apisix.apache.org/http-to-https` |
-| `k8s.apisix.apache.org/http-redirect` |
-| `k8s.apisix.apache.org/http-redirect-code` |
-| `k8s.apisix.apache.org/rewrite-target` |
-| `k8s.apisix.apache.org/rewrite-target-regex` |
-| `k8s.apisix.apache.org/rewrite-target-regex-template` |
-| `k8s.apisix.apache.org/enable-response-rewrite` |
-| `k8s.apisix.apache.org/response-rewrite-status-code` |
-| `k8s.apisix.apache.org/response-rewrite-body` |
-| `k8s.apisix.apache.org/response-rewrite-body-base64` |
-| `k8s.apisix.apache.org/response-rewrite-add-header` |
-| `k8s.apisix.apache.org/response-rewrite-set-header` |
-| `k8s.apisix.apache.org/response-rewrite-remove-header` |
-| `k8s.apisix.apache.org/auth-uri` |
-| `k8s.apisix.apache.org/auth-ssl-verify` |
-| `k8s.apisix.apache.org/auth-request-headers` |
-| `k8s.apisix.apache.org/auth-upstream-headers` |
-| `k8s.apisix.apache.org/auth-client-headers` |
-| `k8s.apisix.apache.org/allowlist-source-range` |
-| `k8s.apisix.apache.org/blocklist-source-range` |
-| `k8s.apisix.apache.org/http-allow-methods` |
-| `k8s.apisix.apache.org/http-block-methods` |
-| `k8s.apisix.apache.org/auth-type` |
-| `k8s.apisix.apache.org/svc-namespace` |
-
### Summary
| Category | Description
|
