Arama Yap Mesaj Submit
Request a Callback
+90
X
X

Select Your Currency

Turkish Lira $ US Dollar Euro
X
X

Select Your Currency

Turkish Lira $ US Dollar Euro

Contact Us

Location Halkali merkez neighborhood fatih st ozgur apt no 46 , Kucukcekmece , Istanbul , 34303 , TR
Last technical review · 17.08.2026 · PDM 1.1

Proxmox Datacenter Manager 1.1: Bring Multiple Clusters Into One Control Plane

PDM does not replace the PVE UI of a single cluster; it adds a central inventory and operations layer across Proxmox environments. Version 1.1 adds installation workflows, centralized subscription keys, local metrics and richer Ceph visibility.

Production note

Do not expose PDM as a public dashboard. Every connected remote creates management authority; use least privilege and a dedicated management network or VPN.

proxmox datacenter manager 1.1pdm 1.1 setupproxmox multi cluster management
TECHNICAL IMPLEMENTATION PROFILE
EKA CORE
PDM 1.1

If you manage multiple PVE clusters, PBS instances or sites, PDM 1.1 improves centralized resource and health visibility. Because it is a management plane, access, token and TLS policy come first.

1.128 May 2026
Checked
13.5Debian Trixie
Checked
Multi-siteCentral view
Checked
CephCluster health visibility
Checked
Technical guide · production-focused · official sources
Quick answer

If you manage multiple PVE clusters, PBS instances or sites, PDM 1.1 improves centralized resource and health visibility. Because it is a management plane, access, token and TLS policy come first.

01

Technical scope at a glance

Use Proxmox Datacenter Manager 1.1 for centralized visibility across multiple PVE/PBS environments, with remote onboarding, permissions, metrics, Ceph visibility and secure access.

1.128 May 2026

Official PDM 1.1 release date.

13.5Debian Trixie

PDM 1.1 shipped on Debian 13.5.

Multi-siteCentral view

Observe multiple PVE/PBS environments from one inventory.

CephCluster health visibility

Version 1.1 expands Ceph monitoring.

On this page

  1. 1. When PDM helps—and when it is unnecessary
  2. 2. Separate the management server from workload VMs
  3. 3. Avoid defaulting to broad admin tokens for remotes
  4. 4. Turn central metrics into alert policy
  5. 5. Tie subscription-key management to asset lifecycle
  6. 6. Protect PDM as a dedicated management zone
  7. Frequently asked questions
02

1. When PDM helps—and when it is unnecessary

The PVE UI may be enough for a single node or small cluster. PDM becomes more valuable as environments, sites and operator count grow.

ScenarioPDM value
1 standalone PVELow
2-3 clustersHigh
Multiple sites/DCsVery high
Central NOC/operationsVery high
03

2. Separate the management server from workload VMs

PDM is not usually compute-heavy; reliable storage, DNS, NTP and controlled management connectivity matter more.

Command
hostnamectl
Command
timedatectl status
Command
ip -br address
Command
ip route
Command
systemctl --failed
04

3. Avoid defaulting to broad admin tokens for remotes

Define which inventory and operations should be available centrally for each remote, then scope tokens and roles accordingly.

Standardize remote identity by site and environment type.
Track token rotation dates in inventory.
Document certificate/fingerprint change procedures.
05

4. Turn central metrics into alert policy

Charts alone are not operations. Map node availability, datastore usage, Ceph health, backup lag and certificate expiry to owners and actions.

SignalExample thresholdAction
Datastore> 80%Review capacity/retention
Ceph HEALTH_WARNCeph HEALTH_WARNCeph HEALTH_WARNInvestigate PG/OSD cause
Node offline> 3 minSite/network/host runbook
06

5. Tie subscription-key management to asset lifecycle

Node additions, removals, hardware replacements and cluster migrations should update subscription inventory too. PDM 1.1 makes this part of central operations.

Track asset ID ↔ node ↔ subscription key mapping.
Add key removal to decommission runbooks.
07

6. Protect PDM as a dedicated management zone

Use VPN/allow lists, 2FA, strong TLS and separate administrator accounts. Compromise of PDM access can affect multiple clusters.

Command
ss -lntp
Command
journalctl -p warning -b --no-pager | tail -100
Command
systemctl --failed
EKA SUNUCU · TECHNICAL

Centralize multiple Proxmox environments without creating one failure domain

Place the PDM management server on Eka Sunucu with network and access policy separated from PVE/PBS clusters.

Production principleMeasure → Test → DeployNo fabricated benchmark data.
SRC

Official sources

Primary documentation and technical references used by this guide.

EKA

Related technical guides

Continue with related infrastructure and implementation guides.

FAQ

Frequently asked questions

PDM 1.1

Does PDM replace the Proxmox VE UI?

No. PDM adds a central view and operations layer across PVE/PBS environments; cluster-specific detail remains available in PVE/PBS.

Which Debian version underlies PDM 1.1?

According to the official release, it is based on Debian 13.5.

Should PDM be internet-exposed?

VPN, a management VLAN or source-IP allow list is safer than broad public exposure.

Is PDM necessary for one cluster?

Usually not. Its strongest value appears with multiple clusters, sites or operations teams.

Top