Skip to content

Support AWS NLB routable QUIC connection IDs #756

@vholer

Description

@vholer

There is a new QUIC support in the AWS Network Load Balancer, which might be used on top of (HAProxy) Kubernetes Ingress. The approach is that AWS NLB controller configures to each pod unique AWS_LBC_QUIC_SERVER_ID env. variable, which should be used to derive the QUIC connection ID. (But, I have to say that I haven't found if the server ID in HAProxy is configurable at all.)

Announcement:
https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-quic-protocol-support-for-network-load-balancer-accelerating-mobile-first-applications/

Example using Envoy proxy (interesting are the steps with namespace labeling and service and pod annotations):
https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/guide/use_cases/quic/

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions