- The Mapping Resource
- Automatic Retries
- Canary Releases
- Circuit Breakers
- Cross-Origin Resource Sharing
- Method-based Routing
- Prefix Regex
- Traffic Shadowing
- Developer Portal
- Edge Policy Console
- The Ambassador Module
- Gzip Compression
- Host CRD, ACME Support, and External Load Balancer Configuration
- Ingress Controller
- Troubleshooting Ambassador
- Custom Filters
- Deploying to Kubernetes from GitHub
- Knative Serverless Framework
- Prometheus monitoring
- Frequently Asked Questions
Ambassador Edge Stack enables you to control timeouts in several different ways.
timeout_ms is the timeout for an entire user-level transaction. By default, this is 3000ms. This spans the point at which the entire downstream request has been processed (i.e., end of stream) to the point where the upstream response has been processed. This timeout includes all retries.
idle_timeout_ms controls how long a connection should remain open when no traffic is being sent through the connection. If not set, Ambassador Edge Stack will wait 5 minutes (300000 milliseconds).
connect_timeout_ms controls the connection-level timeout for Ambassador Edge Stack to an upstream service. The default is
The various timeouts are applied to a Mapping resource and can be combined.
---apiVersion: getambassador.io/v2kind: Mappingmetadata:name: quote-backendspec:prefix: /backend/service: quotetimeout_ms: 4000idle_timeout_ms: 500000connect_timeout_ms: 4000