Is there any doc guide how to integrate with existed Springboot application. in the source code samples "ziti-springboot-client" just see a identity config and in the springboot main class enable ziti. and in scheduled call using RestTemplate call, but for all our existed applications we using regular RestController declaration our APIs and for some of internal service we only provide RPC apis 。 So can some one help answer how to using this to integrate the existed springboot applications including support the RPC calls。As we have thousands of Springboot Apps it will huge work if change all of them using RestTemplate call
Hi @alvin-zj, welcome to the community and to OpenZiti!
Thousands of Springboot apps! Excellent! Can you provide a small sample app somewhere, ideally on GitHub or someplace I/we can clone the source and have a look at what you're doing? A reprentative sample of what you're trying to do really helps us understand exactly what you're looking for. Is that possible?
Hi @TheLumberjack , thanks very much for reply so quickly. Yes I make a simple app in my Github GitHub - alvin-zj/openziti-example: an zero trust project with openziti example , please clone it and have a look. it's just a simple Springboot web apps have only 1 hello API, 80% of our apps are provide reset APIs like this. All I want know is how to integrate the OpenZiti into all these kind of Apps. by the way for the Network part we already installed success.
thanks!
Thanks a lot! It's really helpful. Now I have a network install question. would you please help on it. If we using openziti in our production env. which type you suggestion to using? docker or k8s, or just install on VM? our production env currently is all VM(if not supported, we can put all VM together building an k8s)
Thanks!
You should use the simplest and/or best fitting approach.
If you are using mainly VMs, then you can install OpenZiti also in a VM. I know there are .deb and .rpm packages available.
I use a VM with the official .rpm packages (but they seem to be quite old: openziti-controller is on version 1.1.7 and the .deb package is, if I remember correctly on version 1.5.x).
Interesting. They were not being published for a while but that should have been fixed a few weeks ago. I'll have to check to see if they are still old, they shouldn't be...
I agree with @frm, all three are viable production install methods so it is up to you. i would suggest whatever is easiest for you to scale, in case you need to add cpu or storage etc. whatever your comfortable with
Oh and of course, NetFoundry can take care of production too, scaling, backups, etc if you didn't want the hassle that comes with owning and operating your own production overlay network. There are lots of flexible options there as well.