Follow these guides to get started using Gloo!
- API Gateway
- Setup Options
- Kubernetes Ingress
The API Gateway pattern With the API Gateway pattern, we are explicitly simplifying the calling of a group of APIs to emulate a cohesive API for an “application” for a specific set of users, clients, or consumers. As we use microservices to build our systems, the notion of “application” kind of disappears. The API Gateway pattern helps to restore this notion. The key here is the API gateway, when it’s implemented, becomes the API for clients and applications and is responsible for communicating with any backend APIs and other application network endpoints (those that don’t meet the aforementioned definition of API).
Deployment and Setup Options for running Gloo
Setting up Gloo to handle Kubernetes Ingress Objects.
Google’s Knative project leverages a Kubernetes Cluster Ingress Controller to route requests to apps managed and autoscaled by Knative. At the time of writing, the only available options for Cluster Ingress are Istio and Gloo. This tutorial explains how to get started using Gloo as your Knative Cluster Ingress. What you’ll need kubectl Kubernetes v1.11.3+ deployed somewhere. Minikube is a great way to get a cluster up quickly. Docker installed and running on your local machine, and a Docker Hub account configured (we’ll use it for a container registry).