Allow configuring "apiBaseUrl" generated for badger plugin #1300

Closed
opened 2026-04-05 18:49:49 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @krzwiatrzyk on 6/28/2025

The case: I want to deploy Pangolin additionally to my existing Traefik in Kubernetes cluster (working on a guide how to do that!) and I will have Traefik deployed in traefik namespace and Pangoling deployed in pangolin namespace.

Due to that, apiBaseUrl for badger should be apiBaseUrl: "http://pangolin.pangolin:3001/api/v1" but currently there is no option to configure that in Pangolin configuration file.

Adding such a parameter would unblock me and allow to proceed with more separate setup (that Traefik don't have to be deployed exactly as in the Pangolin docs).

*Originally created by @krzwiatrzyk on 6/28/2025* The case: I want to deploy Pangolin additionally to my existing Traefik in Kubernetes cluster (working on a guide how to do that!) and I will have Traefik deployed in `traefik` namespace and Pangoling deployed in `pangolin` namespace. Due to that, apiBaseUrl for badger should be `apiBaseUrl: "http://pangolin.pangolin:3001/api/v1"` but currently there is no option to configure that in Pangolin configuration file. Adding such a parameter would unblock me and allow to proceed with more separate setup (that Traefik don't have to be deployed exactly as in the Pangolin docs).
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/pangolin#1300