[FEATURE]

[DavidKittleSEL]

Is your feature request related to a problem or a Pull Request

We use k3d to spin up a local development version of our platform, which includes keycloak. The latest version of keycloak relies on X-Forwarded-* headers to properly generate hyperlinks. It looks like the built in k3d loadbalancer (nginx) is not configured to set these X-Forwarded-* headers. which causes keycloak to generate hyperlinks that do not work.

Describe the solution you'd like

K3d config files already have a section for the loadbalancer options.k3d.loadbalancer.configOverrides. I suggest adding an option in this section for enabling X-Forwarded-* headers, perhaps something like settings.use-forwarded-headers=true

options:
  k3d:
    loadbalancer:
      configOverrides:
        - "settings.use-forwarded-headers=true"

Describe alternatives you've considered

Perhaps a new command flag like k3d cluster create --use-forwarded-headers.

[iwilltry42]

Hi @DavidKittleSEL , thanks for opening this issue!

k3d's proxy (k3d--serverlb) does not touch any headers or anything. In fact, it doesn't even operate on the HTTP layer, but on plain TCP and UDP layers using proxy_pass, so it should be fully transparent for your HTTP applications.

I guess, you may want to look into the Traefik Ingress controller configuration, which is not handled by k3d.