Documentation #45377
closed
mgr/dashboard: document Prometheus' security model
Added by Patrick Seidensal almost 4 years ago.
Updated about 3 years ago.
Backport:
octopus nautilus
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/
- Pull request ID set to 34902
- Status changed from In Progress to Resolved
- Target version set to v15.2.4
- Backport changed from octopus to octopus nautilus
- Backport changed from octopus nautilus to octopus
- Backport changed from octopus to octopus nautilus
- Status changed from Resolved to Pending Backport
- Copied to Backport #47227: octopus: mgr/dashboard: document Prometheus' security model added
- Copied to Backport #47228: nautilus: mgr/dashboard: document Prometheus' security model added
- 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".
- Project changed from mgr to Dashboard
- Category changed from 175 to Docs
Also available in: Atom
PDF