Virtual Hosting

Hostname based Routing

Name-based virtual hosts use multiple host names for the same IP address.

foo.bar.com --|               |-> foo.bar.com s1:80
              | load balancer |
bar.foo.com --|               |-> bar.foo.com s2:80

The following Ingress tells the backing loadbalancer to route requests based on the Host header.

apiVersion: voyager.appscode.com/v1beta1
kind: Ingress
metadata:
  name: test-ingress
  namespace: default
spec:
  rules:
  - host: foo.bar.com
    http:
      paths:
      - backend:
          serviceName: s1
          servicePort: '80'
  - host: bar.foo.com
    http:
      paths:
      - backend:
          serviceName: s2
          servicePort: '80'

AppsCode Ingress also support wildcard Name based virtual hosting. If the host field is set to *.bar.com, Ingress will forward traffic for any subdomain of bar.com. so foo.bar.com or test.bar.com will forward traffic to the desired backends.

Cross Namespace traffic routing

If your ingress in namespace foo and your application is in namespace bar you can still forward traffic.

apiVersion: voyager.appscode.com/v1beta1
kind: Ingress
metadata:
  name: test-ingress
  namespace: foo
spec:
  rules:
  - host: foo.bar.com
    http:
      paths:
      - backend:
          serviceName: s1.bar # serviceName.Namespace
          servicePort: '80'

Path based Routing

A setup can be like:

foo.bar.com -> load balancer -> / foo    s1:80
                                / bar    s2:80

would require an Ingress such as:

apiVersion: voyager.appscode.com/v1beta1
kind: Ingress
metadata:
  name: test-ingress
  namespace: default
spec:
  rules:
  - host: appscode.example.com
    http:
      paths:
      - path: "/foo"
        backend:
          serviceName: s1
          servicePort: '80'
      - path: "/bar"
        backend:
          serviceName: s2
          servicePort: '80'

The Ingress controller will provision an implementation specific loadbalancer that satisfies the Ingress, as long as the services (s1, s2) exist.

Take your team where it needs to go.

Create your cluster in minutes. Our team is here to help and would be happy to chat with you.