[GitHub] [apisix-ingress-controller] gxthrj edited a comment on issue #927: Proposal: support external name service

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

gxthrj edited a comment on issue #927:
URL: https://github.com/apache/apisix-ingress-controller/issues/927#issuecomment-1073823636


   > GCP is also actively developing managed istio control plane called traffic director, it can be deployed anywhere and utilise envoy or any xDS v3 compatible data plane to satisfy the requirement we have.
   Ambassador also has a native CRD resoruce mapping to define your service with external url directly https://www.getambassador.io/docs/edge-stack/latest/topics/using/intro-mappings/#introduction-to-the-mapping-resource, the missing part if active health check no sure if it’s supported or not .https://github.com/emissary-ingress/emissary/issues/3761
   Gloo Edge also supports native CRD to configure multi url with active health check and upstream node name passing feature we needed, example config could be found here https://gist.github.com/elvis-cai/d6978b1113edb10359da1358146f61aa.
   
   Yes, The idea is generally the same, I think supporting the feature in `ApisixUpstream` resource as a native CRD is a good idea.


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