Skip to content

Ingress

Ingress manages external access to services in a cluster, typically through HTTP. Ingress may provide load balancing, SSL termination and name-based virtual hosting.

You must have an Ingress controller to satisfy an Ingress. Only creating an Ingress resource has no effect.

The following example will route HTTP requests sent to the /hello url prefix to a service associated with a deployment of the hashicorp/http-echo image.

const helloDeployment = new kplus.Deployment(this, text, {
  containers: [
    {
      image: 'hashicorp/http-echo',
      args: [ '-text', 'hello ingress' ]
    }
  ]
});

const helloService = helloDeployment.expose(5678);

const ingress = new IngressV1Beta1(this, 'ingress');
ingress.addRule('/hello', kplus.IngressV1Beta1Backend.fromService(helloService));

You can use addHostRule(host, path, backend) to define a route that will only apply to requests with this Host header. This can be used to implement virtual hosts.

The addDefaultBackend(backend) and addHostDefaultBackend(host, backend) methods can be used to define backends that will accept all requests that do not match any other rules.

The TCP port used to route requests to services will be determined based on which ports are exposed by the service (e.g. through serve()). If the service exposes multiple ports, then a port must be specified via IngressBackend.fromService(service, { port }.