1 port per geocluster makes envoy only marginally useful

dcoelho

There are MANY scenarios whereby having more than one port on a given FQDN is important. For example, HTTP/HTTPS/SMTP all on the same FQDN. The limitation within envoy such that each of these needs a different FQDN makes envoy useless for many of our applications.

I strongly urge a review of this and enhancement to allow more than one cluster (e.g. port) to be associated with one geocluster so that a single FQDN can support multiple ports per above.

dgautam · Posted: Mon Oct 26, 2009 9:52 pm Post subject:

Thanks for the suggestion. Surely we will review this requirement.

skatsev · Posted: Wed Nov 11, 2009 12:45 pm Post subject:

Thanks for the request. We have reviewed and and agree that this is a useful feature (and indeed would increase the possible Envoy use-cases). We have added this feature to the development road map, but as of right now there is no ETA.

Thanks again!