Installing Emissary-ingress

Install via Helm

Helm, the package manager for Kubernetes, is the recommended way to install Emissary-ingress. Full details are in the Helm instructions.

Install via Kubernetes YAML

Another way to install Emissary-ingress if you are unable to use Helm is to directly apply Kubernetes YAML. See details in the manual YAML installation instructions..

Install Locally on Docker

The Docker install will let you try the Emissary-ingress locally in seconds, but is not supported for production workloads. Try Emissary-ingress on Docker.

Upgrade Options

If you already have an existing installation of Ambassador Edge Stack or Emissary-ingress, you can upgrade your instance:

1. Upgrade to Ambassador Edge Stack from Emissary-ingress.
2. Upgrade your Emissary-ingress instance to the latest version.

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 emissary image from any of the following registries:

• docker.io/emissaryingress/
• 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 Emissary-ingress in Production.

What’s Next?

Emissary-ingress has a comprehensive range of features to support the requirements of any edge microservice. To learn more about how Emissary-ingress works, along with use cases, best practices, and more, check out the Welcome page or read the Emissary-ingress Story.