Skip to content

💡 Add flag to enable WARP routing #1010

@0x2b3bfa0

Description

@0x2b3bfa0

Feature description

When using cloudflared tunnel to connect a network, users have to enable WARP routing by writing a config.yml file or using RemoteConfig as showcased below to let Cloudflare manage the tunnel configuration.

For people using the cloudflare/cloudflared container images, it would be more convenient to expose a --warp-routing flag instead of requiring the presence of a configuration file.

Alternative solutions

terraform {
  required_providers {
    cloudflare = {
      source  = "cloudflare/cloudflare"
      version = ">= 3.29"
    }
  }
}

data "cloudflare_accounts" "main" {
  name = "..."
}

resource "cloudflare_tunnel" "example" {
  account_id = data.cloudflare_accounts.main.accounts[0].id
  ...
  config_src = "cloudflare"
}

resource "cloudflare_tunnel_config" "iterative" {
  account_id = cloudflare_tunnel.example.account_id
  tunnel_id  = cloudflare_tunnel.example.id

  config {
    warp_routing {
      enabled = true
    }

    ingress_rule {
      service = "http_status:404"
    }
  }
}

Additional context

Problem description

While some container orchestrators can easily inject configuration files into containers using e.g. Kubernetes (ConfigMap), others like AWS ECS don't provide any straightforward way of achieving this.

Given that the official cloudflared container images don't even include a shell binary, this use case would require building and hosting a new container image to include the configuration file. Other solutions, like mounting volumes from an ad-hoc sidecar container would be still more cumbersome.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Priority: NormalMinor issue impacting one or more usersType: Feature RequestA big idea that would be split into smaller pieces

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions