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.

Sign up for GitHub

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

Jump to bottom

Investigate alternative possibilities to reduce Prometheus's permissions required to monitor workspaces #15031

Closed
skabashnyuk opened this issue Oct 30, 2019 · 1 comment
Closed

Investigate alternative possibilities to reduce Prometheus's permissions required to monitor workspaces #15031

skabashnyuk opened this issue Oct 30, 2019 · 1 comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.
Milestone
Backlog - Platform

Comments

@skabashnyuk
Copy link
Contributor

Is your task related to a problem? Please describe.

On some cluster setup, cluster-wide permission that is required for Prometheus could become a complicated question.

Describe the solution you'd like

We should evaluate possibilities to reduce/limit these permissions to 0 or minimum.
Variants

  • Investigate the possibility to bridge Theia service from workspace namespace to Prometheus namespace
  • Investigate the possibility to notify Prometheus about newly available services with some API

Describe alternatives you've considered

#14888 cluster-wide permission to list and watch services.

Additional context

#13270
@skabashnyuk skabashnyuk added kind/task Internal things, technical debt, and to-do tasks to be performed. team/platform severity/P1 Has a major impact to usage or development of the system. labels Oct 30, 2019
@skabashnyuk skabashnyuk added this to the Backlog - Platform milestone Oct 30, 2019
@l0rd l0rd mentioned this issue Oct 31, 2019
Closed
11 tasks
@skabashnyuk skabashnyuk mentioned this issue Oct 31, 2019
Closed
@che-bot
Copy link
Contributor

che-bot commented May 12, 2020

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 12, 2020
@che-bot che-bot closed this as completed May 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
Backlog - Platform
Development

No branches or pull requests
2 participants
@skabashnyuk @che-bot