shreemaan-abhishek opened a new pull request, #2875:
URL: https://github.com/apache/apisix-ingress-controller/pull/2875

   ### Type of change:
   
   - [x] Bugfix
   
   ### What this PR does / why we need it:
   
   This change validates both the group and kind of Gateway API ExtensionRef 
filters. The supported reference is `apisix.apache.org/PluginConfig`.
   
   Unsupported group or kind values now set `ResolvedRefs=False` with reason 
`InvalidKind`. Missing PluginConfig or referenced Secret objects set 
`ResolvedRefs=False` with reason `BackendNotFound`.
   
   HTTPRoute and GRPCRoute translation now keeps the route active and adds a 
per-rule `fault-injection` response with status 500 when an ExtensionRef cannot 
be resolved. Other rules on the same route remain active.
   
   Unit coverage includes reference validation, status conditions, HTTPRoute 
and GRPCRoute translation, and ExtensionRef indexers. An end-to-end HTTPRoute 
case verifies both the condition and the 500 response.
   
   Fixes #2841
   
   ### Breaking changes
   
   Rules with invalid or unresolved ExtensionRef filters previously forwarded 
requests without the requested filter. Those rules now return 500. Use 
`apisix.apache.org/PluginConfig` and ensure the referenced PluginConfig and 
Secrets exist. Valid ExtensionRef behavior is unchanged.
   
   ### Pre-submission checklist:
   
   - [x] Did you explain what problem does this PR solve? Or what new features 
have been added?
   - [x] Have you added corresponding test cases?
   - [ ] Have you modified the corresponding document?
   - [ ] Is this PR backward compatible? **If it is not backward compatible, 
please discuss on the [mailing 
list](https://github.com/apache/apisix-ingress-controller#community) first**


-- 
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