Skip to content

Latest commit

 

History

History
42 lines (38 loc) · 1.27 KB

simple-fanout.md

File metadata and controls

42 lines (38 loc) · 1.27 KB
Raw

Simple Fanout

As described previously, pods within kubernetes have ips only visible on the cluster network. So, we need something at the edge accepting ingress traffic and proxy-ing it to right endpoints. This component is usually a highly available loadbalancer(s). An Ingress allows you to keep number of loadbalancers down to a minimum, for example, 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. When it has done so, you will see the address of the loadbalancer under the Status of Ingress.

Next Reading