Skip to content

Route Cloudflare tunnel traffic through the platform gateway #6

Description

@linear-code

The homelab Cloudflare tunnel is network-policy-scoped to platform-envoy-proxy, but the platform Gateway HTTP listener only accepts *.samuelho.space. Cloudflare can terminate TLS for other project domains, then the origin Gateway rejects their hostnames; dev.creativetoolkits.com/webhooks/stripe hangs and Stripe disables the endpoint.

Make the platform Gateway's cleartext HTTP listener hostname-agnostic. HTTPS remains certificate/hostname scoped, and attached HTTPRoutes continue to enforce exact hostnames.

Acceptance: generated Gateway renders an HTTP listener without hostname; Kyverno chart validation passes; no TLS listener scope changes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions