courtmanr@gmail.com
4aa3d7aa5f
The earlier drawer changes left a few surfaces that still looked or behaved differently, plus code nothing used any more: - Proxmox Mail Gateway had two drawers for one gateway; the row now opens the shared resource drawer with mail flow as its Mail tab. The Ceph cluster drawer gains the canonical header, Overview (alerts, Worth checking, capacity history, cards, closed Details) and Manage, and its dot follows the row instead of reading grey on missing health. - The Kubernetes cluster drawer's Deployments tab repeated the Workloads table with dead-end rows; it is gone, and Namespaces opens the Workloads tab scoped to the cluster and namespace with one action. The Docker Swarm drawer tab could not be reached from any page; gone. - On phones, windowed tables (Kubernetes deployments, pods) and the Storage tab's grouped pools stopped at 70-90% of the width: a colspan=100 spacer or colspan=99 group row created phantom columns that took the width hidden columns left. Those rows now span exactly the visible header cells. - The node and Docker host drawers gain the guest drawer's Open action; the Docker host withholds readings while offline or stale, lists operator state first in Manage and shows its action history. A guest's physical disks open the same disk Overview as the Storage tab, with the guest agent's disk temperature alerts. - One "No active alerts" line, one timestamp row and wrapping alert subjects replace per-drawer copies; PBS and PMG alerts match on their instance id so drawers find them without a metrics target. - Removes the old disk detail and its presentation code, the Swarm and Kubernetes Deployments drawers and their presentation helpers, and drawer state nothing read.
Pulse documentation
Start here for installation, platform setup, security, operations, and Pulse Intelligence. Commands, configuration keys, image names, API fields, and product identifiers remain untranslated in localized guides.
Need help with a failure? Read the safe reporting guidance before sharing evidence. A second reproduction or diagnostics export is not required; keep the original evidence if another attempt could interrupt workloads or send duplicate notifications. GitHub reports and attachments are public: review them locally and keep credentials and private details out.
Start here
- Install Pulse — signed Proxmox/Linux installation, Docker, Docker Compose, Kubernetes, and first-run setup.
- Production deployment and security — least-privilege Proxmox setup, root-agent boundaries, discovery, supply-chain verification, plan limits, scale evidence, and a rollout checklist.
- Upgrade from Pulse v5 — migration prerequisites, rollback, agent continuity, and post-upgrade checks.
- Releases and update channels: choosing Stable or Preview, beta and RC expectations, and how releases are tested and promoted.
- Configure Pulse — authentication, notifications, discovery, retention, and system settings.
- Deployment models — data locations, lifecycle, and differences between supported deployment paths.
- Troubleshooting and FAQ — common failures, diagnostics, and operator questions.
Localized getting started guides: Deutsch · Español
Platforms and agents
- Proxmox Backup Server
- Proxmox Mail Gateway
- Docker and Podman
- Kubernetes and Helm
- TrueNAS SCALE and CORE
- Unified Agent
- Agent security
- VM disk monitoring
- ZFS monitoring
- Temperature monitoring
VMware vSphere support is early access. Current builds expose dedicated vSphere inventory and recovery context, but operators should validate the integration against their own vCenter before production use.
Monitoring and operations
- Metrics history
- Recovery data
- Webhooks
- Automatic updates
- Centralized agent management (Pro)
- Operational trust model
- Current product screenshots
Pulse Intelligence
- Assistant, Patrol, and external-agent overview
- Patrol modes and safety
- Assistant safety model
- External agent HTTP and MCP substrate
Patrol watch-only analysis is available on Community with a local model or the operator's own provider. Investigation and governed fixes require the relevant Pulse Pro capabilities.
Security, privacy, and access
- Production deployment and security
- Security review scope
- Authentication and credential storage review packet
- Security guide
- Privacy and telemetry disclosure
- OIDC and SSO
- Proxy authentication
- Role-based access control (Pro)
- Audit logging (Pro)
- Reverse proxy configuration
- Code-signing policy
Plans and managed access
- Community, Relay, and Pro capabilities
- Relay and Pulse Mobile handoff
- Multi-tenant organizations (Enterprise/custom)
- Provider-hosted MSP operations (request-assisted)
Pulse Cloud is not generally available. Ordinary self-hosted Pulse remains the primary installation path; MSP and Enterprise access are explicit commercial paths rather than defaults in self-hosted setup.
Development and reference
Detailed design notes and dated migration specifications may remain in this directory for maintainers, but they are not operator setup guides unless they are linked from the sections above.
Previous versions and migrations
- Upgrade from v4 to v5
- Retired unified-navigation migration — historical context only; current Pulse uses platform-shaped navigation.
- Move a Pulse installation
Found a bug? Use the issue forms. For setup questions, use GitHub Discussions.