Puppet system requirements depend on your deployment type and size. Before installing, ensure your systems are compatible with infrastructure and agent requirements.
The primary server is fairly resource intensive, and must be installed on a robust, dedicated server. The agent service has few system requirements and can run on nearly anything.
|1||2.4||0.5||Amazon Linux 2 AMI|
|1||2.5||1||Windows Server 2019|
The demands on the primary server vary widely between deployments. Resource needs are affected by the number of agents being served, how frequently agents check in, how many resources are being managed on each agent, and the complexity of the manifests and modules in use.
Supported agent platforms
Puppet provides official packages for various operating systems and versions. You aren't necessarily limited to using official packages, but installation and maintenance is generally easier with official tested packages.
puppet-agent packages are available for these
For information on supported operating systems for Puppet Server, visit https://puppet.com/docs/puppet/7/server/install_from_packages.html#supported-operating-systems.
|Operating system||Tested versions||Untested versions|
|macOS||10.15 Catalina, 11 Big Sur (64-bit packages only), 12 Monterey (64-bit packages only), 12 (M1)|
|Microsoft Windows||10 Enterprise, 11 Enterprise (x86_64)||8, 10|
|Microsoft Windows Server||2012R2, 2016, 2019, 2022||2012|
Red Hat Enterprise Linux, including:
||6, 7, 8, 8 Power, 9|
|SUSE Linux Enterprise Server||12 (x86_64), 15 (x86_64)|
|Rocky Linux||8 (x86_64)|
|Oracle Linux||6 (x86_64), 6 (i386), 7 (x86_64), 7 (aarch64), 8 (x86_64), 8 (aarch64), 8 (ppc64le)|
|Scientific Linux||6 (x86_64), 6 (i386), 7 (x86_64), 7 (aarch64), 8 (x86_64), 8 (aarch64), 8 (ppc64le)|
|Ubuntu||18.04, 18.04 AARCH, 20.04, 20.04 AARCH, 22.04 (x86_64)|
- Ruby 2.5.x
- Facter 2.0 or later
- Optional gems such
Timekeeping and name resolution
Before installing , there are network requirements you need to consider and prepare for. The most important requirements include syncing time and creating a plan for name resolution.
Use NTP or an equivalent service to ensure that time is in sync between your primary server, which acts as the certificate authority, and any agent nodes. If time drifts out of sync in your infrastructure, you might encounter issues such as agents recieving outdated certificates. A service like NTP (available as a supported module) ensures accurate timekeeping.
Decide on a preferred name or set of names that agent nodes can use to contact the primary server. Ensure that the primary server can be reached by domain name lookup by all future agent nodes.
simplify configuration of agent nodes by using a CNAME record to make the primary server
reachable at the hostname
puppet, which is the default primary server
hostname that is suggested when installing an agent node.
In the agent-server architecture, your primary server must allow incoming connections on port 8140, and agent nodes must be able to connect to the primary server on that port.