User Guides

Follow these guides to get started using Gloo!

  • Kubernetes Ingress Object
  • Setting up Gloo to handle Kubernetes Ingress Objects.

  • Basic Path Routing
  • Basic routing example for using Gloo to route requests based on query path.

  • Function Routing
  • Creating routing rules to web functions

  • External API Routing
  • Example of routing to an external upstream.

  • Advanced Route Matching
  • Advanced routing matching rules for Gloo.

  • Advanced Route Actions
  • Advanced routing action rules for Gloo.

  • Advanced Route Plugins
  • Advanced routing Plugins for Transformation, retries, timeouts, and other fine grained controls.

  • Cloud Function Routing
  • How to route to cloud function as a service

  • Setting up Server TLS
  • Understanding how to set up TLS for Gloo

  • Exposing Gloo with NodePort
  • Motivation By default, microservices deployed in Kubernetes have an internal flat network that is not accessible from the outside of the cluster. This is true even if you use Kubernetes on a public cloud (like Amazon AWS or Google Cloud). A NodePort service is a way to make Kubernetes services available from outside the cluster (and potentially allow access from the internet) by opening ports on all of the nodes in the cluster and allowing traffic to go directly to the pods running within the cluster.

  • Configure CORS
  • Understanding CORS Cross-Origin Resource Sharing (CORS) is a method of enforcing client-side access controls on resources by specifying external domains that are able to access certain or all routes of your domain. Browsers use the presence of HTTP headers to determine if a response from a different origin is allowed. It is a mechanism which aims to allow requests made on behalf of you and at the same time block requests made by rogue JS.

  • Gloo and Istio mTLS
  • Motivation Serving as the Ingress for an Istio cluster – without compromising on security – means supporting mutual TLS communication between Gloo and the rest of the cluster. Mutual TLS means that the client proves its identity to the server (in addition to the server proving its identity to the client, which happens in regular TLS). For this exercise, you will need Istio installed with mTLS enabled. This guide was tested with istio 1.

  • Gloo and AWS App Mesh
  • Using Gloo as an ingress to App Mesh

  • Gloo with Knative
  • 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).