Open source Puppet is made up of several packages: puppet-agent
, puppetserver
, and, optionally, puppetdb
. Understanding what versions are maintained and which versions go together is important when upgrading and troubleshooting.
Puppet releases and lifecycle
- Developmental releases: Puppet versions not associated with any PE version release new minor (or "y") version about once a month. Developmental releases typically do not get patch (or "z") releases. Each minor release in this stream supersedes the previous minor release. Documentation for the current developmental release is available at puppet.com/docs/puppet/latest. See the release notes for updates to this release stream.
- Long-term releases: Puppet versions associated with Puppet Enterprise get patch (or "z") releases a few times a year. Each release contains fixes and features from several developmental releases. Versioned documentation for long-term releases is available at puppet.com/docs/puppet/<X.Y> (for example, puppet.com/docs/puppet/6.4).
Puppet version | Puppet Server version | PuppetDB version | Associated PE version | EOL date |
---|---|---|---|---|
6.10.1 (latest) | 6.7.1 | 6.7.1 | none | Superseded by next developmental release. |
6.4.x | 6.3.x | 6.3.x | 2019.1.x | February 2020 |
5.5.x | 5.3.x | 5.2.x | 2018.1.x | May 2020 |
For information about Puppet's operating system support, see the platform support lifecycle page.
Puppet packages
-
puppet-agent
- This package contains Puppet’s main code and all of the dependencies needed to run it, including Facter, Hiera, and bundled versions of Ruby and OpenSSL. After it’s installed, you have everything you need to run the Puppet agent service and the
puppet apply
command. -
puppetserver
- Puppet Server is a JVM-based application that, among other things, runs instances of the Puppet master application and serves catalogs to nodes running the agent service. It has its own version number and might be compatible with more than one Puppet version. This package depends on
puppet-agent
. After it’s installed, Puppet Server can serve catalogs to nodes running the agent service. -
puppetdb
- PuppetDB (optional) collects data generated by Puppet. It enables additional features such as exported resources, advanced queries, and reports about your infrastructure.
puppet-agent
component version numbers
Each puppet-agent
package contains several components. This table shows the components shipped in this release track, and contains links to available component release notes. Agent release notes are included on the same page as Puppet release notes.
puppet-agent | Puppet | Facter | Hiera | Resource API | Ruby | OpenSSL |
---|---|---|---|---|---|---|
6.10.1 | 6.10.0 | 3.14.5 | 3.6.0 | 1.8.9 | 2.5.7 | 1.1.1d |
6.10.0 | 6.10.0 | 3.14.5 | 3.6.0 | 1.8.8 | 2.5.3 | 1.1.1a |
6.9.0 | 6.9.0 | 3.14.4 | 3.5.0 | 1.8.7 | 2.5.3 | 1.1.1a |
6.8.0 | 6.8.0 | 3.14.3 | 3.5.0 | 1.8.6 | 2.5.3 | 1.1.1a |
6.7.2 | 6.7.2 | 3.14.2 | 3.5.0 | 1.8.6 | 2.5.3 | 1.1.1a |
6.7.1 | This version of Puppet was never released. | |||||
6.7.0 | 6.7.0 | 3.14.2 | 3.5.0 | 1.8.6 | 2.5.3 | 1.1.1a |
6.6.0 | 6.6.0 | 3.14.1 | 3.5.0 | 1.8.5 | 2.5.3 | 1.1.1a |
6.5.0 | 6.5.0 | 3.14.0 | 3.5.0 | 1.8.4 | 2.5.3 | 1.1.1a |
6.4.0 | 6.4.0/ | 3.13.1 | 3.5.0 | 1.8.1 | 2.5.3 | 1.1.1a |
6.3.0 | 6.3.0 | 3.13.0 | 3.5.0 | 1.7.0 | 2.5.3 | 1.1.1a |
6.2.0 | 6.2.0 | 3.12.3 | 3.5.0 | 1.6.3 | 2.5.3 | 1.1.1a |
6.1.0 | 6.1.0 | 3.12.2 | 3.5.0 | 1.6.2 | 2.5.3 | 1.1.0h |
6.0.0 | 6.0.0 | 3.12.0 | 3.4.5 | 1.5.0 | 2.5.1 | 1.1.0h |
Master and agent compatibility
Use this table to verify that you're using a compatible version of the agent for your PE or Puppet master.
Master | |||||
---|---|---|---|---|---|
PE 3.x Puppet 3.x | PE 2015.1 through 2017.2 Puppet 4.x | PE 2017.3 through 2018.1 Puppet 5.x | PE 2019.1 and later Puppet 6.x | ||
Agent | 3.x | ✓ | ✓ | ✓ | ✓ |
4.x | ✓ | ✓ | ✓ | ||
5.x | ✓ | ✓ | |||
6.x | ✓ |
- Puppet 3.x has reached end of life and is not actively developed or tested. We retain agent 3.x compatibility with later versions of the master only to enable upgrades.
-
You can use pre-6.x agents with a Puppet 6.x or PE 2019.0 or later master, but this combination doesn't take advantage of the new intermediate certificate authority architecture introduced in Puppet Server 6.0. To adopt the new CA architecture, both your master and agents must be upgraded to at least 6.x/2019.0, and you must regenerate certificates. If you don't upgrade all of your nodes to 6.x, do not regenerate your certificates, because pre-6.x agents won't work with the new CA architecture.