ztunnel
ztunnel copied to clipboard
Scalability of ztunnel
It might be a bit early, but there are some specific use case scenarios that I have when using it, as follows:
- The Protocol between ztunnel (HBONE)
- Alternative other implementations
- More LB algorithms support ,such as least connection 、wrr (for waypoint canary upgrade)
- DNS Proxy
- Support external others Discovery Server (such as Eureka 、Nacos、Zookeeper, etc)
- Support DNS rewrite or others
- Access Log
What is actually the request here? None of his seems to be about "scalability" and it isn't clear what is being asked.
We have access logs for example
What is actually the request here? None of his seems to be about "scalability" and it isn't clear what is being asked.
We have access logs for example
@howardjohn Ztunnel supports extensible development capabilities, this could be similar to plugins in CoreDNS or filters in Envoy.
Can you please give specific examples of what you want? Ztunnel is very specifically not a general purpose extensible proxy but instead a specialized proxy for the use case it is deployed in. So while we may offer some extensibility at some point, it's unlikely we will ever offer the degree of something like Envoy. So it's important to understand the use cases