rcourtman
2cc5814282
The license server broker pins one Pulse Pro release, and that release can be a prerelease. The Pro update check already skips a prerelease pin on the stable channel, and apply already refuses it. The runtime switch check from #2949 skipped that rule, so: - an in-place stable install saw a switch offer that always failed at apply with "stable channel cannot install prerelease builds" - a Docker stable install got digest-pinned commands that moved it onto the preview Pro image Changes: - `stableChannelRefusesProPin` in `internal/updates/pro_update.go` is now the single rule for the Pro update check, the runtime switch check and apply. - `CheckProRuntimeSwitch` returns `available: false` with the new reason `prerelease_only` and the pinned `version`. This happens before the in-place and Docker branches, so neither path offers the pin. Installs on the rc channel are still offered it. - Regression tests cover: the stable channel refusing a pin flagged as a prerelease, a pin whose version is a prerelease without the flag, and a same-version flagged pin; the configured default channel; the rc channel still offered the pin; and apply refusing before any download with the message the API maps to 409. A separate API test keeps that refusal a 409 with the message passed through, not the generic 500. Follow-ups outside this PR: - The Updates card (#2983, not yet on main) does not know `prerelease_only` and shows nothing for it. Copy for it is in a PR stacked on that branch. Contracts: `api-contracts.md` adds `prerelease_only` to the closed `reason` set for `GET /api/updates/pro-runtime`, and `deployment-installability.md` records that the switch check shares the stable-channel guard. The commit no longer carries a Contract-Neutral trailer. Replaces #3007, rebuilt on current main with those contract notes.
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.