Open bsctl opened 3 years ago
@prometherion getting interest in this feature, we should prioritise it. Could you provide an impact analysis from architectural pov?
I'm working on this, scouting some already existing projects to understand if we can plugin them or not.
Plugging the prom-label-proxy
handlers doesn't sound so smooth, at least from a DX perspective.
In fact, the end-users would be required to add always a label to their metrics, and this could be annoying: for Namespace filtering, we decided to go for kubectl get namespaces
without the need to add -l capsule.clastix.io/teanant=oil
and I think the same should apply also for metrics.
WDYT @bsctl ?
@prometherion it makes sense
Here a list of Prometheus endpoints that should be handled by the proxy:
/api/v1/query
/api/v1/query_range
/api/v1/series
/api/v1/labels
/api/v1/label/<name>/values
/api/v1/rules
/api/v1/alerts
/api/v2/silences
/federate
Investigate if the capsule-proxy can enforce the tenant label in a given PromQL query, in Prometheus API responses, and in Alert Manager API requests as prom-label-proxy does.