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://www.getambassador.io.

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

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 stderr:

Since this hook is required for Helm 2 support it IS NOT AN ERROR AND CAN BE SAFELY IGNORED.

Install with Helm

When you run the Helm chart, it installs Emissary-ingress. You can deploy it with either version of the tool.

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

2. Helm 2 users: Install the Emissary-ingress Chart with the following command:

3. Set up Service Catalog to view all of your service metadata in Ambassador Cloud.

Create a Mapping

In a typical configuration workflow, Custom Resource Definitions (CRDs) are used to define the intended behavior of Emissary-ingress. In this example, we'll deploy a sample service and create a Mapping resource. Mappings allow you to associate parts of your domain with different URLs, IP addresses, or prefixes.

1. First, apply the YAML for the “Quote of the Moment" service.

2. Copy the configuration below and save it to a file called quote-backend.yaml so that you can create a Mapping on your cluster. This Mapping tells Emissary-ingress to route all traffic inbound to the /backend/ path to the quote Service.

3. Apply the configuration to the cluster by typing the command kubectl apply -f quote-backend.yaml.

4. Grab the IP of your Emissary-ingress

5. Test the configuration by typing curl -Lk https://$EMISSARY_LB_ENDPOINT/backend/ or curl -Lk https://<hostname>/backend/. You should see something similar to the following:

A single source of configuration

In Emissary-ingress, Kubernetes serves as the single source of configuration. This enables a consistent configuration workflow.

1. To see your mappings via the command line, run kubectl get mappings

2. If you created Mappings or other resources in another namespace, you can view them by adding -n <namespace> to the kubectl get command or add -A to view resources from every namespace. Without these flags, you will only see resources in the default namespace.

Upgrading an existing Emissary-ingress installation

Note: If your existing installation is running Emissary-ingress, do not use these instructions. 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 (as of Helm 3, this is not supported in the chart itself):

2. Next, upgrade Emissary-ingress itself:

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

3. Set up Service Catalog to view all of your service metadata in Ambassador Cloud.

Migrating to Ambassador Edge Stack

If you have an existing Emissary-ingress installation but are not yet running Ambassador Edge Stack, the upgrade process is somewhat different than above.

Note: It is strongly encouraged for you to move your Emissary-ingress release to the ambassador namespace as shown below. If this isn't an option for you, remove the --namespace ambassador argument to helm upgrade.

1. Upgrade CRDs for Emissary-ingress.

   To take full advantage of Emissary-ingress, you'll need the new Host CRD, and you'll need the new getambassador.io/v2 version of earlier CRDs. To upgrade all the CRDs, run

2. Upgrade your Emissary-ingress installation.

   If you're using Helm 3, simply run

   If you're using Helm 2, you need to modify the command slightly:

At this point, Ambassador Edge Stack should be running with the same functionality as Emissary-ingress as well as the added features of Ambassador Edge Stack. It's safe to do any validation required and roll-back if necessary.

Note: Ambassador Edge Stack will be installed with an AuthService and RateLimitService. If you are using these plugins, set authService.create=false and/or rateLimit.create=false to avoid any conflict while testing the upgrade.

Test your Mapping over HTTPS after upgrading to Ambassador Edge Stack

Upgrading to Ambassador Edge Stack will provide automatic TLS support if you have not already configured it.

1. Grab the IP of your Ambassador Edge Stack

   • Note: Make sure to remove -n ambassador if you decided to not migrate to the ambassador namespace when upgrading to Ambassador Edge Stack

2. Try submitting a request to the quote service that you deployed above