Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scalability of ztunnel #852

Open
zengyuxing007 opened this issue Mar 15, 2024 · 3 comments
Open

Scalability of ztunnel #852

zengyuxing007 opened this issue Mar 15, 2024 · 3 comments

Comments

@zengyuxing007
Copy link

zengyuxing007 commented Mar 15, 2024

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
@howardjohn
Copy link
Member

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

@zengyuxing007
Copy link
Author

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.

@howardjohn
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants