- The Mapping Object
- 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
- Knative Serverless Framework
- Prometheus monitoring
- Frequently Asked Questions
Since Ambassador Edge Stack's configuration is entirely stored in Kubernetes resources, no special process is necessary to upgrade Ambassador Edge Stack. If you're using the YAML files supplied by Datawire, you'll be able to upgrade simply by repeating the following
kubectl apply commands.
First, determine if Kubernetes has RBAC enabled:
kubectl cluster-info dump --namespace kube-system | grep authorization-mode
If you see something like
--authorization-mode=Node,RBAC in the output, then RBAC is enabled.
If RBAC is enabled:
kubectl apply -f https://www.getambassador.io/yaml/aes-crds.yaml
If RBAC is not enabled:
kubectl apply -f https://www.getambassador.io/yaml/aes.yaml
This will trigger a rolling upgrade of Ambassador Edge Stack.
If you're using your own YAML, check the Datawire YAML to be sure of other changes, but at minimum, you'll need to change the pulled
image for the Ambassador Edge Stack container and redeploy.