[GitHub] [apisix-ingress-controller] Iced-Sun commented on issue #664: request help: ingress/apisixroute without physical service backends

[GitBox <gi...@apache.org>]

Iced-Sun commented on issue #664:
URL: https://github.com/apache/apisix-ingress-controller/issues/664#issuecomment-913124170


   > It seems your problem can be solved by:
   > 
   >     1. Support to use Nginx variables in route match;
   > 
   >     2. Just use the `plugin` field in ApisixRoute.
   
   The problem I see with `ApisixRoute` is migration and mental burden.
   
   As mentioned in #629, most existing ingresses must be migrated to `ApisixRoute`. IMHO, `ApisixRoute` is somewhat a custom version of the native Ingress. Extending the native Ingress instead of a custom analog should be more friendly to users and seem to be a common approach.
   
   An ingress without physical service backends also enable routing with `actions` without backends. For instance, to redirect http to https, a service backend must be assigned in current implementation, but the service is never really used. Such behavior leads to more maintenance and more error-prone.


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org