Skip to content
master
Go to file
Code

Latest commit

* comment out cloudbuild to test faster github actions
* create temp test, remove other tests for now
* Merge branch 'master' into i3415-make-focused-tests-fail
* correct temp test format, try installing ginkgo
* Merge branch 'i3415-make-focused-tests-fail' of https://github.com/solo-io/gloo into i3415-make-focused-tests-fail
* add commands before codegen to try making code check script visible
* try using ginkgo
* move ginkgo install to front
* move ginkgo install back to original pos
* print procelain status to see what's up
* add go sum change
* try go get instead of install
* specifically target makefile install location
* undo mod/sum changes
* add ginkgo flags we like
* try focusing something
* unfocus test
* revert reg tests yaml to original + ginkgo
* uncomment cloudbuild
* changelog file
* remove ellipses from test target
* recomment cloudbuild and remove most tests
* dont use _output to ref ginkgo
* comment out more stuff to backtrack
* move ginkgo existance testing to its own test sectino
* double check gobin location
* try test-in-makefile strategy
* use all normal reg test actions
* actually run 1 test
* test focus failure
* Adding changelog file to new location
* Deleting changelog file from old location
* add useful comments/remove test comments/ tentative final test
* Merge branch 'master' of https://github.com/solo-io/gloo into i3415-make-focused-tests-fail
* merge CL conflicts
* remove extra test stuff
* Adding changelog file to new location
* Deleting changelog file from old location
* Merge branch 'master' into i3415-make-focused-tests-fail
* Merge branch 'master' into i3415-make-focused-tests-fail
* CL typo correction
e3b6c0c

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
ci
 
 
 
 
 
 
 
 
 
 
 
 
pkg
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

README.md

Gloo
An Envoy-Powered API Gateway

Gloo is a feature-rich, Kubernetes-native ingress controller, and next-generation API gateway. Gloo is exceptional in its function-level routing; its support for legacy apps, microservices and serverless; its discovery capabilities; its numerous features; and its tight integration with leading open-source projects. Gloo is uniquely designed to support hybrid applications, in which multiple technologies, architectures, protocols, and clouds can coexist.

Installation   |   Documentation   |   Blog   |   Slack   |   Twitter |   Enterprise Trial


Gloo Architecture

Summary

Using Gloo

  • Kubernetes ingress controller: Gloo can function as a feature-rich ingress controller, built on top of the Envoy Proxy.
  • Next-generation API gateway : Gloo provides a long list of API gateway features, including rate limiting, circuit breaking, retries, caching, external authentication and authorization, transformation, service-mesh integration, and security.
  • Hybrid apps: Gloo creates applications that route to backends implemented as microservices, serverless functions, and legacy apps. This feature can help users to gradually migrate from their legacy code to microservices and serverless; can let users add new functionalities using cloud-native technologies while maintaining their legacy codebase; can be used in cases where different teams in an organization choose different architectures; and more. See here for more on the Hybrid App paradigm.

What makes Gloo unique

  • Function-level routing allows integration of legacy applications, microservices and serverless: Gloo can route requests directly to functions, which can be a serverless function call (e.g. Lambda, Google Cloud Function, OpenFaaS function, etc.), an API call on a microservice or a legacy service (e.g. a REST API call, OpenAPI operation, XML/SOAP request etc.), or publishing to a message queue (e.g. NATS, AMQP, etc.). This unique ability is what makes Gloo the only API gateway that supports hybrid apps, as well as the only one that does not tie the user to a specific paradigm.
  • Gloo incorporates vetted open-source projects to provide broad functionality: Gloo support high-quality features by integrating with top open-source projects, including gRPC, GraphQL, OpenTracing, NATS and more. Gloo's architecture allows rapid integration of future popular open-source projects as they emerge.
  • Full automated discovery lets users move fast: Upon launch, Gloo creates a catalog of all available destinations, and continuously maintains it up to date. This takes the responsibility for 'bookkeeping' away from the developers, and guarantees that new feature become available as soon as they are ready. Gloo discovers across IaaS, PaaS and FaaS providers, as well as Swagger, gRPC, and GraphQL.
  • Gloo integrates intimately with the user's environment: with Gloo, users are free to choose their favorite tools for scheduling (such as K8s, Nomad, OpenShift, etc), persistence (K8s, Consul, etcd, etc) and security (K8s, Vault).

Next Steps

Thanks

Gloo would not be possible without the valuable open-source work of projects in the community. We would like to extend a special thank-you to Envoy.

Security

Reporting security issues: We take Gloo's security very seriously. If you've found a security issue or a potential security issue in Gloo, please DO NOT file a public Github issue, instead send your report privately to security@solo.io.

You can’t perform that action at this time.