Michal Szakala

Hello @BlowaXD , not sure if this is still relevant but you could use environment variables to build the URL dynamically, something like: `endpoint_url "http://#{ENV['SENTRY_KUBE_DSN_KEYS']}@#{ENV['SENTRY_KUBE_HOST']}:#{ENV['SENTRY_KUBE_PORT']}/#{ENV['SENTRY_KUBE_PROJECT_ID']}"`

I'm not sure I understand your setup. Let's say you have 3 machines. So you have 3 FluentD forwarders, right? Is it one FluentD service and 3 pods on different...

You can still use FluentD environment variables and reference Sentry endpoint configuration from labels using `fieldRef` in your Kubernetes Deployment definition. FluentD config example: `endpoint_url "http://#{ENV['SENTRY_KUBE_DSN_KEYS']}@#{ENV['SENTRY_KUBE_HOST']}:#{ENV['SENTRY_KUBE_PORT']}/#{ENV['SENTRY_KUBE_PROJECT_ID']}"` And your Kubernetes Deployment...