Developers can work on Gloo Edge in a number of different ways. You can contribute to Gloo Edge open-source, help with documentation, or extend Gloo Edge’s functionality via the addition of plugins.
You can contribute to the Gloo Edge open-source project by logging issues, generating PRs, or helping with documentation. More information about contributing to Gloo Edge can be found in our Contributing section.
Gloo Edge invites developers to extend Gloo Edge’s functionality and adapt to new use cases via the addition of plugins.
Gloo Edge’s plugin based architecture makes it easy to extend functionality in a variety of areas:
- Gloo Edge’s API: extensible through the use of Protocol Buffers along with Solo-Kit
- Service Discovery Plugins: automatically discover service endpoints from catalogs such as Kubernetes and Consul
- Function Discovery Plugins: annotate services with information discovered by polling services directly (such as OpenAPI endpoints and gRPC methods).
- Routing Plugins: customize what happens to requests when they match a route or virtual host
- Upstream Plugins: customize what happens to requests when they are routed to a service
- Operators for Configuration: Gloo Edge exposes its intermediate language for proxy configuration via the
gloo.solo.io/ProxyCustom Resource, allowing operators to leverage Gloo Edge for multiple use cases. The Gloo Edge gateway and Sqoop provide API Gateway and GraphQL Server functionality respectively, without needing to run in the same process (or even the same container) as Gloo Edge.
To get started with development around Gloo Edge, we recommend taking a look at our Developer Guides.