I was speaking to an OpenZiti community member with private DMs recently. After the conversation, they said we share the conversation anonymised which should be valuable for others too.
User:
Hi Philip,
Thank you for your welcome! I’m fine answering your questions
Currently we have a varied bunch of ‘solutions’ - Bastion hosts, Site2Site VPN’s, Terminal Server stuff and even Customer-VPN-Clients installed on our employee client machines… My intention is to standardize this and present a smart solution. Also regarding all the GPDR and all related stuff here in Europe
My research started with https://goteleport.com/ which didn’t fit our needs and so we finally landed at guacomole (yeah, I’ve seen your BrowZer showcase) for the CLI and Windows desktop stuff, but there was no solution for HTTP or even Port-Tunneling. And after a long research and testing I found OpenZITI which looks very promizing
What has been your experience so far?
There are thing that look very fresh (Documentation, tutorials, … )and still being in a change (integrating router etc, into one binary, some conceptional changes when reading older docs, …) but on the other end it seems that there are also components looking very mature (Desktop / Mobile clients, API, UI, …). OpenZITI is very flexible, but this also bring’s a bit of a complexity that has to be learned
What use case are you focused on yourself?
I think I’ve explained my overall use case answering the 1st question. The Java connector would be for an application allowing the technicans to ‘open up connections’ on demand when working on tickets.
An other idea we have is to interconnect some internal services between separate kubernetes clusters, but this is currently only a rough idea.
What do you think we could do to improve the project?
Grow, get a bigger and greater community!
Maybe also have an eye on all the ‘cloud native’ (kubernetes) things and folks. Having it easily deployed and configured within a kubernetes infrastructure might be a goal. And also an (kubernetes) operator interacting with kubernets would be a nice option:
- Automatically Registering routers / ‘hosts’ (endpoint) when they get deployed
- When assigning intercept roles to a kubernetes deployed endpoint the operator could create service objects to announce the service and redirect things to the endpoint
- Also it could look for services having special annotations and automatically create the appropiate service configuration within the ziti controller
Quite a lot idea’s but this would be the next step