- 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
- Custom Error Responses
- Gzip Compression
- Host CRD, ACME Support, and External Load Balancer Configuration
- Ingress Controller
- Troubleshooting Ambassador
- Deploying to Kubernetes from GitHub
- Knative Serverless Framework
- Prometheus monitoring
- Frequently Asked Questions
Helm is a package manager for Kubernetes that automates the release and management of software on Kubernetes. The Ambassador Edge Stack can be installed via a Helm chart with a few simple steps, depending on if you are deploying for the first time, upgrading the Ambassador Edge Stack from an existing installation, or migrating from the Ambassador API Gateway.
The Ambassador Edge Stack Helm chart is hosted by Datawire and published at
Start by adding this repo to your helm client with the following command:
helm repo add datawire https://www.getambassador.io
Both Helm 2 and Helm 3 are supported. To enable CRD creation in Helm 2, the
crd-install hook is included in the CRD manifests. When installing with Helm 3, the following message will be output to
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
Since this hook is required for Helm 2 support it IS NOT AN ERROR AND CAN BE SAFELY IGNORED.
When you run the Helm chart, it installs the Ambassador Edge Stack. You can deploy it with either version of the tool.
If you are installing the Ambassador Edge Stack for the first time on your cluster, create the
ambassadornamespace for the Ambassador Edge Stack:kubectl create namespace ambassador
Helm 3 users: Install the Ambassador Edge Stack Chart with the following command:helm install ambassador --namespace ambassador datawire/ambassador
Helm 2 users: Install the Ambassador Edge Stack Chart with the following command:helm install --name ambassador --namespace ambassador datawire/ambassador
Finish the installation by running the following command:
edgectl install(optional) *
Provide an email address when prompted to receive notices if your domain or TLS certificate is about to expire. (optional)
Your terminal should print something similar to the following:
$ edgectl install-> Installing the Ambassador Edge Stack 1.0.-> Existing Ambassador Edge Stack installation detected.-> Automatically configuring TLS.Please enter an email address. We’ll use this email address to notify you prior to domain and certification expiration [None]: firstname.lastname@example.org.-> Obtaining a TLS certificate from Let’s Encrypt.Congratulations, you’ve successfully installed the Ambassador Edge Stack in your Kubernetes cluster. Visit https://random-word.edgestack.me to access your Edge Stack installation and for additional configuration.
* Edge Control (
edgectl) automatically configures TLS for your instance and provisions a domain name for your Ambassador Edge Stack. This is not necessary if you already have a domain name and certificates.
This will install the necessary deployments, RBAC, Custom Resource Definitions, etc. for the Ambassador Edge Stack to route traffic. Details on how to configure Ambassador using the Helm chart can be found in the Helm chart README.
Note: If your existing installation is running the Ambassador API Gateway, do not use these instructions. See Migrating to the Ambassador Edge Stack instead.
Upgrading an existing installation of the Ambassador Edge Stack is a two-step process:
First, apply any CRD updates (as of Helm 3, this is not supported in the chart itself):kubectl apply -f https://www.getambassador.io/yaml/aes-crds.yaml
Next, upgrade the Ambassador Edge Stack itself:helm upgrade ambassador datawire/ambassador
This will upgrade the image and deploy and other necessary resources for the Ambassador Edge Stack.
If you have an existing Ambassador API Gateway installation but are not yet running the Ambassador Edge Stack, the upgrade process is somewhat different than above.
Note: It is strongly encouraged for you to move your Ambassador release to the
ambassador namespace as shown below. If this isn't an option for you, remove the
--namespace ambassador argument to
Upgrade CRDs for the Ambassador Edge Stack.
To take full advantage of the Ambassador Edge Stack, you'll need the new
HostCRD, and you'll need the new
getambassador.io/v2version of earlier CRDs. To upgrade all the CRDs, runkubectl apply -f https://www.getambassador.io/yaml/aes-crds.yaml
Upgrade your Ambassador installation.
If you're using Helm 3, simply runhelm upgrade --namespace ambassador ambassador datawire/ambassador
If you're using Helm 2, you need to modify the command slightly:helm upgrade --set crds.create=false --namespace ambassador ambassador datawire/ambassador
At this point, the Ambassador Edge Stack should be running with the same functionality as Ambassador API Gateway as well as the added features of the Ambassador Edge Stack. It's safe to do any validation required and roll-back if necessary.
Note: The Ambassador Edge Stack will be installed with an
RateLimitService. If you are using these plugins, set
rateLimit.create=false to avoid any conflict while testing the upgrade.