Control traffic with policies
Use Gloo Gateway policies to control the traffic within your cluster environment. Review the following available policies or learn how to apply policies to your resources.
Active healthcheckUse the ingress gateway to periodically check the health of an upstream service in your cluster.
Connection pool settings for HTTPUse a connection policy to configure connection pool settings for an HTTP destination.
Connection pool settings for TCPSet up connection pool settings for a TCP destination, such as TCP keepalive.
Fault injectionTest the resilience of your apps by injecting delays and connection failures.
Outlier detectionConfigure Gloo to remove unhealthy destinations from the connection pool, and add the destinations back when they become healthy again.
RetryReduce transient failures and hanging systems by setting retries and timeouts.
TimeoutReduce transient failures and hanging systems by setting retries and timeouts.
Enable TLS origination on your ingress gateway so that you can accept incoming HTTP requests, encrypt them, and forward the requests to services that only accept HTTPS connections.
CORSEnforce client-site access controls with cross-origin resource sharing (CORS).
CSRFApply a CSRF filter to the gateway to help prevent cross-site request forgery attacks.
Data Loss PreventionApply a CSRF filter to the gateway to help prevent cross-site request forgery attacks.
External authSet up an external authentication and authorization to protect the workloads in your cluster. For example, you can set up basic, passthrough, API key, OAuth, OPA, or LDAP authentication.
JWTControl access or route traffic based on verified claims in a JSON web token (JWT).
WAFFilter, monitor, and block potentially harmful HTTP traffic with a Web Application Firewall (WAF) policy.
Traffic control policies
Header manipulationAppend or remove HTTP request and response headers at the route level.
HTTP buffer filterSet the maximum request body size that you want to accept for a particular workload in your cluster.
Listener connectionChange the default connection buffer limit that is set for each gateway listener to ensure large requests can be properly sent and received by the gateway.
Load balancer and consistent hashSpecify how you want the ingress gateway to select an upstream service to serve an incoming client request.
MirrorDuplicate outgoing traffic to test a new app.
Proxy protocolPreserve connection information such as the client IP address for traffic that goes through your gateway listener.
Rate limitControl the rate of requests to a destination or route.
TransformationAlter a request before matching and routing, such as with an Inja header template.
Gloo Mesh service mesh workload policies
You can use the following policies to log or control traffic to service mesh workloads in east-west scenarios.
To use this feature, you must have a Gloo Mesh license in addition to your Gloo Gateway license.
AccessControl access for workloads in your service mesh environment.
FailoverUse a failover policy to determine where to reroute traffic in case of failure.
WebAssembly (Wasm) deploymentAdd a Wasm filter to the Envoy sidecar proxy, for use cases such as customizing the endpoints and thresholds for your workloads.