Skip to content

Switch to Gateway API for TCP and HTTP service ingress #64

@detjensrobert

Description

@detjensrobert

Ingress is so last year....

Currently TCP challenges are exposed via individual LoadBalancer services, not through ingress. Worked, but not great to create several cloud provider LoadBalancers if we dont need to. The new Gateway api supports TcpRoute resources to do TCP level routing (great).

Keep challenges on individual domains, but point them all at the same IP / ingress LB on unique ports.

Metadata

Metadata

Assignees

No one assigned

    Labels

    damctf postmortemThings identified during/after DamCTF that need attention

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions