gateway-charts/ingress.yaml at main · starburstdata/gateway-charts · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: gateway-ingress
  annotations:
    # Ingress Core Settings
    kubernetes.io/ingress.class: "alb"
    alb.ingress.kubernetes.io/inbound-cidrs: 100.40.95.150/32, 73.227.21.253/32
    alb.ingress.kubernetes.io/target-type: ip
    alb.ingress.kubernetes.io/listen-ports: '[{"HTTPS":443}]'
    alb.ingress.kubernetes.io/healthcheck-port: '8090'
    # health check the app port to avoid getting sucked into the redirect logic and health checking a backend

    # If TLS is enabled and the AWS load balancer controller is used, then the aws load balancer controller will be unable to provision
    # an LB unless a cert for this host exists in ACM. Upload or create your certificate before installing this chart.
    alb.ingress.kubernetes.io/scheme: internet-facing
spec:
  rules:
    - host: request.wilhelm-gateway.starburst-customer-success.com
      http:
        paths:
          - pathType: Prefix
            path: /
            backend:
              service:
                name: gateway
                port:
                  number: 8080
    - host: app.wilhelm-gateway.starburst-customer-success.com
      http:
        paths:
          - pathType: Prefix
            path: /
            backend:
              service:
                name: gateway
                port:
                  number: 8090
    - host: admin.wilhelm-gateway.starburst-customer-success.com
      http:
        paths:
          - pathType: Prefix
            path: /
            backend:
              service:
                name: gateway
                port:
                  number: 8091