DocsEdge Stack2.2Installing Ambassador Edge Stack
Installing Ambassador Edge Stack
Install with Helm
Helm, the package manager for Kubernetes, is the recommended way to install Ambassador Edge Stack. Full details are in the Helm instructions.
Install with Kubernetes YAML
Another way to install Ambassador Edge Stack if you are unable to use Helm is to directly apply Kubernetes YAML. See details in the manual YAML installation instructions..
Try the demo with Docker
The Docker install will let you try the Ambassador Edge Stack locally in seconds, but is not supported for production workloads. Try Ambassador Edge Stack on Docker.
Upgrade or migrate to a newer version
If you already have an existing installation of Ambassador Edge Stack or Emissary-ingress, you can upgrade your instance. The migration matrix shows you how.
Container Images
Although our installation guides will favor using the docker.io
container registry,
we publish Ambassador Edge Stack and Emissary-ingress releases to multiple registries.
Starting with version 1.0.0, you can pull the aes image from any of the following registries:
docker.io/datawire/
gcr.io/datawire/
We want to give you flexibility and independence from a hosting platform's uptime to support your production needs for Ambassador Edge Stack or Emissary-ingress. Read more about Running Ambassador Edge Stack in Production.
What’s Next?
Ambassador Edge Stack has a comprehensive range of features to support the requirements of any edge microservice. To learn more about how Ambassador Edge Stack works, along with use cases, best practices, and more, check out the Welcome page or read the Ambassador Edge Stack Story.