kayx23 opened a new pull request, #2776:
URL: https://github.com/apache/apisix-ingress-controller/pull/2776

   ## Summary
   - refresh the Apache APISIX Ingress Controller docs for the released `2.1.0` 
feature surface
   - replace the stale `ApisixConsumer` limitation note with a real APISIX CRD 
consumer-plugin example
   - extend the examples page to cover `BackendTrafficPolicy.healthCheck`, 
consumer labels, and `Body` scope route matching
   - update the overview compatibility table to include `2.1.0`
   - update the CRD resource overview to mention consumer-scoped plugins and 
propagated consumer labels
   
   ## Why
   The generated API reference already reflects the `2.1.0` API surface, but 
several operator-facing docs and examples had not caught up yet. In particular:
   - `docs/en/latest/reference/example.md` still said `ApisixConsumer` could 
not configure plugins on consumers
   - the examples page did not surface `BackendTrafficPolicy.healthCheck`
   - the examples page did not show `Body` scope matching or propagated 
consumer labels
   - the overview compatibility table still topped out at `2.0.0`
   
   ## Validation
   Validated against the local `2.1.0` test environment used for the parallel 
API7 docs refresh work:
   - APISIX CRD consumer-scoped plugins on `ApisixConsumer` were re-verified
   - APISIX CRD `Body` scope route matching was re-verified with matching and 
non-matching JSON payloads
   - upstream health checks in `2.1.0` were previously re-verified in the same 
environment and the docs example now reflects that released shape
   
   ## Notes
   - I did not run a full local docs build in this repo during this pass.
   - This PR focuses on the user-facing docs gap for `2.1.0`; the generated API 
reference was already up to date.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to