Connecting External Registries to Istio
Retio is the short word for Registries to Istio, which is capable to communicate with Service Registries and Service Mesh (Istio). It is an easy-to-use and extendable adaptor if you have a service registry and intend to integrate it with Istio. You can just deploy it and tell it which service registries you want to talk to, then it will start to work, and Istio will identify the services in the registries.
While service mesh becomes an important infrastructure for microservices, more and more developers are trying to use Service Mesh like Istio and putting it into production. Also there are many open source service registry projects for discovering services, such as Polaris, Consul, Nacos, ZooKeeper, ETCD, Eureka. So Retio is designed to integrate these registries infrastructures with Istio easily. Just give Retio one or more registry addresses, then it is done and you do not need to wrong about anything else.
- Provide an easy-to-use way to integrate Istio with Registries by MCP and Service Entries.
- Provide an 1 to more model to integrate Istio with more than one Registries at the same time.
- Provide an easy and extendable approach to implement the new Service Registry Models.
- Provide different options to deploy Retio in Kubernetes, so you can choose one as you like.
Clone the project and run:
git clone https://github.com/aeraki-mesh/retio.git- Support ServiceEntry Conventions
- Polaris
- Consul
- Nacos
- ZooKeeper
- ETCD
- Eureka
- .........
- Support Mesh Configuration Protocol (MCP)
- Polaris
- Consul
- Nacos
- ZooKeeper
- ETCD
- Eureka
- .........
- Support Different Deployment Mode
- Quick Start
- Helm Chart
- Kubernetes Operator
Contributions are always welcome!
See contributing.md for ways to get started.
Please read the Code of Conduct
Distributed under the Apache License 2.0 . See LICENSE.txt for more information.
Mail List: [email protected]
Project Link: https://github.com/aeraki-mesh/retio