Project

General

Profile

Documentation #45377

mgr/dashboard: document Prometheus' security model

Added by Patrick Seidensal 5 months ago. Updated 6 days ago.

Status:
Resolved
Priority:
Normal
Category:
dashboard/documentation
Target version:
% 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/


Related issues

Copied to mgr - Backport #47227: octopus: mgr/dashboard: document Prometheus' security model Resolved
Copied to mgr - Backport #47228: nautilus: mgr/dashboard: document Prometheus' security model Resolved

History

#1 Updated by Patrick Seidensal 5 months ago

  • Pull request ID set to 34902

#2 Updated by Patrick Seidensal 5 months ago

  • Backport set to octopus

#3 Updated by Sebastian Wagner 4 months ago

  • Status changed from In Progress to Resolved
  • Target version set to v15.2.4

#4 Updated by Patrick Seidensal 24 days ago

  • Backport changed from octopus to octopus nautilus

#5 Updated by Patrick Seidensal 24 days ago

  • Backport changed from octopus nautilus to octopus

#6 Updated by Patrick Seidensal 24 days ago

  • Backport changed from octopus to octopus nautilus

#7 Updated by Patrick Seidensal 24 days ago

  • Status changed from Resolved to Pending Backport

#8 Updated by Patrick Seidensal 24 days ago

  • Copied to Backport #47227: octopus: mgr/dashboard: document Prometheus' security model added

#9 Updated by Patrick Seidensal 24 days ago

  • Copied to Backport #47228: nautilus: mgr/dashboard: document Prometheus' security model added

#10 Updated by Nathan Cutler 6 days 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".

Also available in: Atom PDF