Control traffic with policies
Use Gloo policies to control the traffic within your service mesh environment. Review the following available policies or learn more about Policy enforcement.
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.
FailoverUse a failover policy to determine where to reroute traffic in case of failure.
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.
Retry and timeoutReduce transient failures and hanging systems by setting retries and timeouts.
Trim proxy configTrim the number of destinations in the Istio sidecar proxy configuration for your workloads to avoid memory pressure issues.
AccessControl access for workloads in your service mesh.
CORSEnforce client-site access controls with cross-origin resource sharing (CORS).
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.
Traffic control policies
Header manipulationAppend or remove HTTP request and response headers at the route level.
Load balancer and consistent hashingSpecify how you want Istio to select an upstream service to serve an incoming client request.
MirrorDuplicate outgoing traffic, to test a new app.
Rate limitControl the rate of requests to destinations within the service mesh.
TransformationAlter a request before matching and routing, such as with an Inja header template.
WebAssembly (Wasm) deploymentAdd a Wasm filter to the Envoy sidecar proxy, for use cases such as customizing the endpoints and thresholds for your workloads.
Gloo Gateway ingress policies
You can use the following policies to control traffic through the ingress gateway in north-south scenarios.
To use this feature, you must have a Gloo Gateway license in addition to your Gloo Mesh license.
Active healtheckUse the ingress gateway to periodically check the health of an upstream service in your cluster.
Client TLSEnable TLS origination for your ingress gateway so that you can encrypt requests before they are forwarded to HTTPS services in your cluster.
CSRFApply a CSRF filter to the gateway to help prevent cross-site request forgery attacks.
HTTP buffer filterSet the maximum request body size that you want to accept for a particular workload in your cluster.
JWTControl access or route traffic based on verified claims in a JSON web token (JWT).
Listener connectionConfigure connection settings between downstream services and a gateway listener.
WAFFilter, monitor, and block potentially harmful HTTP traffic with a Web Application Firewall (WAF) policy.