Ingress specification¶
This document covers how ingress resources work in relation to The AWS Load Balancer Controller.
- Beginning from v2.4.3 of the AWS LBC, rules are ordered as follows:
pathType: Exact
paths are always ordered first- followed by
pathType: Prefix
paths, with the longest prefix first - followed by
pathType: ImplementationSpecific
paths, in the order they are listed in the manifest
An example ingress, from example is as follows.
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: "2048-ingress"
namespace: "2048-game"
labels:
app: 2048-nginx-ingress
spec:
ingressClassName: alb
rules:
- host: 2048.example.com
http:
paths:
- path: /*
pathType: ImplementationSpecific
backend:
service:
name: "service-2048"
port:
number: 80
The host field specifies the eventual Route 53-managed domain that will route to this service.
The service, service-2048, must be of type NodePort in order for the provisioned ALB to route to it.(see echoserver-service.yaml)
The AWS Load Balancer Controller does not support the resource
field of backend
.