Skip to content

R1: Loadbalancer deploy propagates full proxy deploy_options #1

Closed

Description

@mhenrixon

The loadbalancer tier rebuilds deploy flags from scratch and silently drops the rich per-app options (timeouts, buffering, health checks, path prefixes, error pages), and hardcodes target port :80 ignoring app_port and proxy.run.publish/options.

Fix: Kamal::Commands::Loadbalancer#deploy/#run should reuse Proxy#deploy_options instead of re-implementing flag construction; respect app_port; respect proxy.run.publish/options.

Anchor: lib/kamal/commands/loadbalancer.rb:19-20,37-48. Found via integration failures on 2026-07-03.

Verify: integration suite deploys a multi-host app through the LB with custom proxy settings and they take effect; bin/test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinggemLegacy: the gem side of cross-repo work (every item in this repo is)size:SSmall: hours

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions