- 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
If you currently have the open source API Gateway version of Ambassador, you can upgrade to the Ambassador Edge Stack with a few simple commands. When you upgrade to the Ambassador Edge Stack, you'll be able to access additional capabilities such as automatic HTTPS/TLS termination, Swagger/OpenAPI support, API catalog, Single Sign-On, the Edge Policy Console UI, and more. For more about the differences between Edge Stack and the API Gateway, see the Editions page.
edgectl can automate the upgrade from installations that match the following criteria:
- the Ambassador API Gateway has been installed (and is still managed by) the Ambassador Operator.
edgectl by following the instructions
Then, use the following command to upgrade the Ambassador API Gateway installation to Ambassador Edge Stack:
- You must have properly installed Ambassador previously following these instructions.
- You must have TLS configured and working properly on your Ambassador instance
To upgrade your instance of Ambassador:
- Apply the Migration Manifest
- Test the New Deployment
- Redirect Traffic
- Delete the Old Deployment
- Update and Restart
- What's Next?
Make sure that you follow the steps in the given order - not doing that might crash your Ambassador installation or make it inconsistent.
First, install the Ambassador Edge Stack alongside your existing Ambassador installation so you can test your workload against the new deployment.
Note: Make sure you apply the manifests in the same namespace as your current Ambassador installation.
Use the following command to install the Ambassador Edge Stack, replacing
kubectl apply -n <namespace> -f https://www.getambassador.io/yaml/oss-migration.yaml
At this point, you have the Ambassador API Gateway and the Ambassador Edge Stack running side by side in your cluster. The Edge Stack is configured using the same configuration (Mappings, Modules, etc) as your current Ambassador.
Get the IP address to connect to the Ambassador Edge Stack by running the following command:
kubectl get service test-aes -n <namespace>
Test that AES is working properly.
Once you’re satisfied with the new deployment, update your current Ambassador service to redirect traffic to the Ambassador Edge Stack.
Edit the current Ambassador service with
kubectl edit service -n <namespace> ambassador and change the selector to
You can now safely delete the older Ambassador deployment and AES service.
kubectl delete deployment -n <namespace> ambassadorkubectl delete service -n <namespace> test-aes
Apply the new CRDs, resources and restart the Ambassador Edge Stack pod for changes to take effect:
kubectl apply -n <namespace> -f https://www.getambassador.io/yaml/aes-crds.yaml && \kubectl apply -n <namespace> -f https://www.getambassador.io/yaml/resources-migration.yaml && \kubectl rollout restart deployment/aes
You can now access the Edge Policy Console with the following options:
edgectl login -n <namespace> <AES_host>or
Now that you have the Ambassador Edge Stack up and running, check out the Getting Started guide for recommendations on what to do next and take full advantage of its features.