- The Mapping Resource
- Automatic Retries
- Canary Releases
- Circuit Breakers
- Cross-Origin Resource Sharing
- Method-based Routing
- Prefix Regex
- Traffic Shadowing
- Developer Portal
- 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
Sometimes you may want traffic from Ambassador Edge Stack to your services to be encrypted. For the cases where terminating TLS at the ingress is not enough, Ambassador Edge Stack can be configured to originate TLS connections to your upstream services.
Telling Ambassador Edge Stack to talk to your services over HTTPS is easily configured in the
Mapping definition by setting
https:// in the
---apiVersion: getambassador.io/v2kind: Mappingmetadata:name: basic-tlsspec:prefix: /service: https://example-service
If your upstream services require more than basic HTTPS support (e.g. minimum TLS version support or SNI support) you can create a
TLSContext for Ambassador Edge Stack to use when originating TLS.
---apiVersion: getambassador.io/v2kind: TLSContextmetadata:name: tls-contextspec:secret: self-signed-certmin_tls_version: v1.3sni: some-sni-hostname
Configure Ambassador Edge Stack to use this
TLSContext for connections to upstream services by setting the
tls attribute of a
---apiVersion: getambassador.io/v2kind: Mappingmetadata:name: mapping-with-tls-contextspec:prefix: /service: https://example-servicetls: tls-context
example-service service must now support TLS v1.3 for Ambassador Edge Stack to connect.
TLSContext requires a certificate be provided even if not using it to terminate TLS. For origination purposes, this certificate can simply be self-signed unless mTLS is required.