What's the difference between host.v1 and host.v2 configurations?
Also can I use ziti-tunneler-client.v1 and ziti-tunneler-server.v1 ?
We appreciate it when threads are related to the topic. Don't be afraid to open more than one. 
I have made your question a new top-level topic.
The major difference between host.v1 and host.v2 is that host.v2 allows you to specify an array of host.v1 configs. I believe there are other differences too, but I personally generally use host.v1 for example configs because they are a bit smaller.
See Builtin Config Types | OpenZiti and the sub-categories for more information
1 Like
You can, however i don't recommend it. At some point those will be removed.
What's the point of grouping multiple host.v1 configs if we can then only attach them to 1 intercept config ?
I guess Ziti wouldn't know where to route the intercepted traffic if the service has an array of host.v1 attached to a single intercept.v1 doesn't it ?
I don't exactly follow the question. The configs are quite flexible. If you find a situation that isn't covered, I'm happy to explore solutions.
It sounds to me like you are thinking of host configs only in terms of matching a set of intercepts.
A service may have no intercepts for use by SDK clients, or a single intercept that matches a single IP/hostname. Let's say we want to provide access to an HTTP service that is hosted by a bunch of endpoints.
A host.v2 config could have an endpoint defined for each of the HTTP servers, resulting in a terminator for each one, with traffic being load balanced across them.
On the other hand, you might have a tunneler directly on each HTTP server, with a single host config that points to localhost, and each tunneler creating a terminator for itself. The end result would look the same, just a question of where you want hosting software to sit.
There are a couple of videos covering HA services that go into more detail about the choices you can make.
Cheers,
Paul
2 Likes