Configuration for multi tenancy in Jaeger V2 #9625
Replies: 2 comments
|
Update after the later correction below: please do not use my original YAML fragment as the final v2 query-extension config. The better/current v2 shape is the one @vynazevedo pointed out: for the extensions:
jaeger_query:
multi_tenancy:
enabled: true
header: x-tenant
tenants: [tenant-a, tenant-b]The important distinction is that the old |
|
There is a v1/v2 distinction in the earlier example. The v1 flag parser reads For the query extension, the source-derived fragment is: extensions:
jaeger_query:
multi_tenancy:
enabled: true
header: x-tenant
tenants: [tenant-a, tenant-b]Merge that into a complete configuration with your existing Sources at This only addresses query-side tenancy. Receiver metadata propagation and tenant-aware storage must be configured consistently as well; the fragment does not establish end-to-end tenant isolation. Check the exact v2 release and backend, then verify write/read separation with two tenants and rejection of an unlisted tenant. I have checked the configuration types, not run that integration test. |
Uh oh!
There was an error while loading. Please reload this page.
In Jaeger v1, multi-tenancy can be configured using the following flags:
--multi-tenancy.enabled=true
--multi-tenancy.header=x-tenant
--multi-tenancy.tenants=tenant-a,tenant-b
What is the equivalent configuration for multi-tenancy in Jaeger v2?
Specifically, where and how should we configure the equivalent of these three settings in the Jaeger v2 configuration?
All reactions