In this guide, we'll walk you through installing Emissary-ingress in your Kubernetes cluster.
The manual install process does not allow for as much control over configuration as the Helm install method, so if you need more control over your Emissary-ingress installation, it is recommended that you use helm.
Emissary-ingress is designed to run in Kubernetes for production. The most essential requirements are:
- Kubernetes 1.11 or later
Emissary-ingress is typically deployed to Kubernetes from the command line. If you don't have Kubernetes, you should use our Docker image to deploy Emissary-ingress locally.
In your terminal, run the following command:
Determine the IP address or hostname of your cluster by running the following command:
Your load balancer may take several minutes to provision your IP address. Repeat the provided command until you get an IP address.
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.
ListenerResource is required to configure which ports the Emissary-ingress pods listen on so that they can begin responding to requests.
MappingResouce is used to configure routing requests to services in your cluster.
HostResource configures TLS termination for enablin HTTPS communication.
- Explore how Emissary-ingress configures communication with clients
See the migration matrix for instructions about upgrading Emissary-ingress.