Cortex Gateway is a microservice which strives to help you administrating and operating your Cortex Cluster in multi tenant environments.
- Authentication of Prometheus & Grafana instances with JSON Web Tokens
- Prometheus & Jager instrumentation, compatible with the rest of the Cortex microservices
If you run Cortex for multiple tenants you need to identify your tenants every time they send metrics or query them. This is needed to ensure that metrics can be ingested and queried separately from each other. For this purpose the Cortex microservices require you to pass a Header called
X-Scope-OrgID. Unfortunately the Prometheus Remote write API has no config option to send headers and for Grafana you must provision a datasource to do so. Therefore the Cortex k8s manifests suggest deploying an NGINX server inside of each tenant which acts as reverse proxy. It’s sole purpose is proxying the traffic and setting the
X-Scope-OrgID header for your tenant.
We try to solve this problem by adding a Gateway which can be considered the entry point for all requests towards Cortex (see Architecture). Prometheus and Grafana can both send a self contained JSON Web Token (JWT) along with each request. This JWT carries a claim which is the tenant’s identifier. Once this JWT is validated we’ll set the required
X-Scope-OrgID header and pipe the traffic to the upstream Cortex microservices (distributor / query frontend).
||Upstream HTTP URL for Cortex Distributor||(empty string)|
||Upstream HTTP URL for Cortex Query Frontend||(empty string)|
||HMAC secret to sign JSON Web Tokens||(empty string)|
Expected JWT payload
The expected Bearer token payload can be found here: https://github.com/rewe-digital/cortex-gateway/blob/b74de65d10a93e1ec0d223e92c08d16d59bbf3c4/gateway/tenant.go
- “version” (must be an integer)
The audience and version claim is currently unused, but might be used in the future (e. g. to invalidate tokens).
Forked from: https://github.com/rewe-digital/cortex-gateway