Redirect a client ¶

The Nais platform support two ways to exposing your application, either via an Ingress resource, or through service discovery. This means that we also support two ways to redirect your application.

Ingress ¶

To redirect traffic from one domain to another, you need to define an ingress from the old domain that redirects to the new domain, with .spec.redirects[].

The redirects field specifies URL redirects. It is structured as a mapping from a source URL to a target URL.

A successful redirect will return a 302 Moved Temporarily HTTP status code with location header set to the target URL.

metadata:
    annotations:
        nais.io/allow-redirect: "true"

Structure ¶

apiVersion: nais.io/v1alpha1
kind: Application
spec:
  ingress:
    - https://<MY-SUBDOMAIN-NEW>.<ENVIRONMENT-DOMAIN>
  redirects:
    - from: https://<MY-SUBDOMAIN-OLD>.<ENVIRONMENT-DOMAIN>
      to: https://<MY-SUBDOMAIN-NEW>.<ENVIRONMENT-DOMAIN>

Parameters ¶

Usage Example ¶

apiVersion: nais.io/v1alpha1
kind: Application
spec:
  ingress:
    - http://example-new.nais.io
  redirects:
    - from: "http://example-old.nais.io"
      to: "http://example-new.nais.io"

In this example:

Service discovery ¶

To redirect traffic coming through service discovery you need to create a service in the old namespace pointing to the new app/service in the new namespace. This is not a part of the Nais application specification, so you need to create and deploy a separate file for this.

Structure ¶

apiVersion: v1
kind: Service
metadata:
  name: old-appname-redirect # Replace
  namespace: old-namespace # Replace
spec:
  type: ExternalName
  ports:
    - port: 443
  externalName: old-appname.old-namespace.svc.cluster.local # Replace

Deploy either through Github Actions, or using kubectl apply -f .nais/service.yaml.