Developers can work on Gloo in a number of different ways. You can contribute to Gloo open-source, help with documentation, or extend Gloo’s functionality via the addition of plugins.
You can contribute to the Gloo open-source project by logging issues, generating PRs, or helping with documentation. More information about contributing to Gloo can be found in our Contributing section.
Gloo invites developers to extend Gloo’s functionality and adapt to new use cases via the addition of plugins.
Gloo’s plugin based architecture makes it easy to extend functionality in a variety of areas:
- Gloo’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 exposes its intermediate language for proxy configuration via the
gloo.solo.io/ProxyCustom Resource, allowing operators to leverage Gloo for multiple use cases. The Gloo 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.
To get started with development around Gloo, we recommend taking a look at our Developer Guides.