>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. Elvis Cai <elvis....@airwallex.com> 于2022年3月21日周一 20:01写道： > +1, multi external url support with active health check and upstream node > pass is the major block before we rollout Apisix ingress controller in all > of our kubernetes clusters. > It’s quite common for an organisation to expose services internally or > externally in hybrid environment without the boundaries of kubernetes > cluster concept, you can easily have your apps running in serverless > platform, kubernetes cluster in cloud and in bare metal server on your > on-premise data center. > > 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. > > > > On 2022/03/21 01:34:06 Jintao Zhang wrote: > > I have seen some voices in the community, hoping that APISIX Ingress can > > proxy external services e.g: [1], [2] > > > > For these two types of requirements, it is a relatively simple > requirement > > for [1], we only need to add the corresponding External name type service > > to complete. > > > > But for [2], I found a very interesting situation. No other Ingress > > controller implements similar functionality yet, and I think this would > be > > a huge feature. > > > > APISIX actually supports setting the domain name to nodes in the > upstream. > > But APISIX Ingress is not yet supported. > > > > To achieve the above function, we can set a special resolveGranularity to > > directly convert the record of external name to Node. > > > > To achieve the above function, we can set a special resolveGranularity to > > directly convert the record of external name to Node. > > > > > > WDYT? > > > > > > [1]: [ > > > https://github.com/apache/apisix-ingress-controller/issues/813](https://github.com/apache/apisix-ingress-controller/issues/813) > > > > [2]: [ > > > https://github.com/apache/apisix-ingress-controller/issues/645](https://github.com/apache/apisix-ingress-controller/issues/645) > >
