Install with Helm

Helm is a package manager for Kubernetes that automates the release and management of software on Kubernetes. Emissary-ingress can be installed via a Helm chart with a few simple steps, depending on if you are deploying for the first time, upgrading Emissary-ingress from an existing installation, or migrating from Emissary-ingress.

Before you begin

The Emissary-ingress Helm chart is hosted by Datawire and published at https://app.getambassador.io.

Start by adding this repo to your helm client with the following command:

Install with Helm

When you run the Helm chart, it installs Emissary-ingress.

1. Install the Emissary-ingress Chart with the following command:

2. Next Steps

   Emissary-ingress shold now be successfully installed and running, but in order to get started deploying Services and test routing to them you need to configure a few more resources.

   • The Listener Resource is required to configure which ports the Emissary-ingress pods listen on so that they can begin responding to requests.
   • The Mapping Resouce is used to configure routing requests to services in your cluster.
   • The Host Resource configures TLS termination for enablin HTTPS communication.
   • Explore how Emissary-ingress configures communication with clients
   We strongly recommend following along with our Quickstart Guide to get started by creating a Listener, deploying a simple service to test with, and setting up a Mapping to route requests from Emissary-ingress to the demo service.

For more advanced configuration and details about helm values, please see the helm chart.

Upgrading an existing installation

Note: Do not use these instructions to migrate from Emissary-ingress to Ambassador Edge Stack. See Migrating to Ambassador Edge Stack instead.

Upgrading an existing installation of Emissary-ingress is a two-step process:

1. First, apply any CRD updates:

2. Next, upgrade Emissary-ingress itself:

   This will upgrade the image and deploy and other necessary resources for Emissary-ingress.