Puppet system requirements depend on your deployment type and size. Before installing, ensure your systems are compatible with infrastructure and agent requirements.
Hardware requirements
The master 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.
| CPUs | GHz | GiB memory | OS |
|---|---|---|---|
| 1 | 2.4 | 0.5 | Amazon Linux 2 AMI |
| 1 | 2.5 | 1 | Windows Server 2019 |
The demands on the master 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.
| Node volume | Cores | Heap |
ReservedCodeCache
|
|---|---|---|---|
| dozens | 2 | 1 GB | n/a |
| 1,000 | 2-4 | 4 GB | 512m |
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.
Packaged platforms
puppet-agent
packages are available for these platforms.
| Operating system | Tested versions | Untested versions |
|---|---|---|
| Debian | 8, 9, 10 | |
| Fedora | 30 | |
| macOS | 10.14 Mojave (see note below), 10.15 Catalina | |
| Microsoft Windows | 10 Enterprise | 7, 8, 10 |
| Microsoft Windows Server | 2008R2, 2012R2, 2016, 2019 | 2008, 2012 |
Red Hat Enterprise Linux, including:
|
5, 6, 7, 8 | |
| SUSE Linux Enterprise Server | 15 | |
| Ubuntu | 16.04, 18.04, 20.04 |
Dependencies
- Ruby 2.5.x
- CFPropertyList 2.2 or later
- Facter 2.0 or later
-
The
msgpackgem, if you're using msgpack serialization
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.
Timekeeping
Use NTP or an equivalent service to ensure that time is in sync between your master, 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.
Name resolution
Decide on a preferred name or set of names that agent nodes can use to contact the master. Ensure that the master can be reached by domain name lookup by all future agent nodes.
You can
simplify configuration of agent nodes by using a CNAME record to make the master
reachable at the hostname puppet, which is the default master
hostname that is suggested when installing an agent node.
Firewall configuration
In the agent-master architecture, your master must allow incoming connections on port 8140, and agent nodes must be able to connect to the master on that port.