Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should we support per-tenant store endpoints? #69

Open
bill3tt opened this issue Jun 7, 2021 · 1 comment
Open

Should we support per-tenant store endpoints? #69

bill3tt opened this issue Jun 7, 2021 · 1 comment

Comments

@bill3tt
Copy link

bill3tt commented Jun 7, 2021

Currently prom-label-proxy does not support tenants being able to retrieve stores that present their identifying label set.

As this endpoint is not parameterised, implementation would presumably follow the pattern established by the /api/v1/rules endpoint here.

Example response from the Katacoda multi-tenancy tutorial
❯ curl -s https://2886795272-39091-frugo01.environments.katacoda.com/api/v1/stores | jq
{
"status": "success",
"data": {
  "sidecar": [
    {
      "name": "127.0.0.1:19190",
      "lastCheck": "2021-06-07T21:31:22.183374877Z",
      "lastError": null,
      "labelSets": [
        {
          "cluster": "eu1",
          "replica": "0",
          "tenant": "team-fruit"
        }
      ],
      "minTime": -62167219200000,
      "maxTime": 9223372036854776000
    },
    {
      "name": "127.0.0.1:19191",
      "lastCheck": "2021-06-07T21:31:22.182829172Z",
      "lastError": null,
      "labelSets": [
        {
          "cluster": "eu1",
          "replica": "0",
          "tenant": "team-veggie"
        }
      ],
      "minTime": -62167219200000,
      "maxTime": 9223372036854776000
    },
    {
      "name": "127.0.0.1:19192",
      "lastCheck": "2021-06-07T21:31:22.182868637Z",
      "lastError": null,
      "labelSets": [
        {
          "cluster": "eu1",
          "replica": "1",
          "tenant": "team-veggie"
        }
      ],
      "minTime": -62167219200000,
      "maxTime": 9223372036854776000
    }
  ]
}
}

The absence of implementation of this endpoint makes me think that it was deliberately excluded, for what I assume is the potential to leak sensitive information. Since I could not find a public reference to this, I opened this issue instead :)

@simonpasquier
Copy link
Contributor

I'm not sure that we ever discussed this feature to be honest. I think it would be fine to have though it only applies to Thanos and not Prometheus.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants