Actions
Documentation #45377
closedmgr/dashboard: document Prometheus' security model
% Done:
0%
Tags:
monitoring
Backport:
octopus nautilus
Reviewed:
Affected Versions:
Pull request ID:
Description
As Prometheus' security model may not be obvious, we should document how Prometheus, by default, sees it and provide references to this perception.
For example, access to the Prometheus HTTP API cannot be password protected by configuring Prometheus and is, by default, considered to be accessible by untrusted users.
It is presumed that untrusted users have access to the Prometheus HTTP endpoint and logs.
-- https://prometheus.io/docs/operating/security/
Updated by Sebastian Wagner almost 4 years ago
- Status changed from In Progress to Resolved
- Target version set to v15.2.4
Updated by Patrick Seidensal over 3 years ago
- Backport changed from octopus to octopus nautilus
Updated by Patrick Seidensal over 3 years ago
- Backport changed from octopus nautilus to octopus
Updated by Patrick Seidensal over 3 years ago
- Backport changed from octopus to octopus nautilus
Updated by Patrick Seidensal over 3 years ago
- Status changed from Resolved to Pending Backport
Updated by Patrick Seidensal over 3 years ago
- Copied to Backport #47227: octopus: mgr/dashboard: document Prometheus' security model added
Updated by Patrick Seidensal over 3 years ago
- Copied to Backport #47228: nautilus: mgr/dashboard: document Prometheus' security model added
Updated by Nathan Cutler over 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Updated by Ernesto Puerta about 3 years ago
- Project changed from mgr to Dashboard
- Category changed from 175 to Docs
Actions