Files
Pulse/docs
rcourtman 9cfcdbb247 fix: Use per-node shared flag for storage deduplication
The storage deduplication logic only checked cluster config's Shared
flag, but this required the cluster config API call to succeed. When
the per-node storage API already returns shared=1 (as the user
verified), we should use that directly.

Now we check three sources for shared storage detection:
1. Per-node API shared flag (storage.Shared)
2. Cluster config shared flag (if available)
3. Storage type heuristics (NFS, RBD, PBS, etc.)

Related to #1049
2026-01-07 10:16:23 +00:00
..

📚 Pulse Documentation

Welcome to the Pulse documentation portal. Here you'll find everything you need to install, configure, and master Pulse.


🚀 Getting Started

  • Installation Guide Step-by-step guides for Docker, Kubernetes, and bare metal.
  • Configuration
    Learn how to configure authentication, notifications (Email, Discord, etc.), and system settings.
  • Deployment Models
    Where config lives, how updates work, and what differs per deployment.
  • Migration Guide
    Moving to a new server? Here's how to export and import your data safely.
  • Upgrade to v5
    Practical upgrade guidance and post-upgrade checks.
  • FAQ
    Common questions and quick answers.

🛠️ Deployment & Operations

🔐 Security

  • Security Policy The core security model (Encryption, Auth, API Scopes).

New in 5.0

  • Pulse AI Optional assistant for chat, patrol findings, alert analysis, and execution workflows.
  • Metrics History Persistent metrics storage with configurable retention.
  • Mail Gateway Proxmox Mail Gateway (PMG) monitoring.
  • Auto Updates One-click updates for supported deployments.
  • Kubernetes Helm deployment (ingress, persistence, HA patterns).

🚀 Pulse Pro

Pulse Pro unlocks AI Patrol — automated background monitoring that spots issues before they become incidents.

📡 Monitoring & Agents

💻 Development


Found a bug or have a suggestion?

GitHub Issues