To see open issues and things which are in progress see: Crafty Overview. This will give you a view over puppetdb, puppetserver and crafty itself.
The version schema has the following layout:
<puppet.major>.<puppet.minor>.<puppet.patch>-v<container.major>.<container.minor>.<container.patch>
Example usage:
docker pull ghcr.io/voxpupuli/puppetserver:8.6.1-latest| Name | Description |
|---|---|
| puppet.major | Describes the contained major Puppet version (7 or 8) |
| puppet.minor | Describes the contained minor Puppet version |
| puppet.patch | Describes the contained patchlevel Puppet version |
| container.major | Describes the major version of the base container (Ubunutu 22.04) or incompatible changes |
| container.minor | Describes new features or refactoring with backward compatibility |
| container.patch | Describes if minor changes or bugfixes have been implemented |
In puppet/oss example we bundle puppetserver, puppetdb, postgres, puppetboard and HDM together.
We use the images from
- voxpupuli/puppetserver
- voxpupuli/puppetdb
- voxpupuli/puppetboard
- PostgreSQL 16 Alpine
- betadots/hdm
For a comprehensive understanding of our setup, please refer to the detailed information provided in the dedicated README.md.
In our puppet/ha example, we have established a robust infrastructure consisting of a Certificate Authority (CA) server and three Puppet compile servers. To ensure high availability and efficient distribution of workloads, we've incorporated a NGINX load balancer. Additionally, there's a dedicated test node for thorough testing and validation.
For a comprehensive understanding of our setup, please refer to the detailed information provided in the dedicated README.md.
In puppet/minimal example we bundle puppetserver, puppetdb and postgres together.
For a comprehensive understanding of our setup, please refer to the detailed information provided in the dedicated README.md.
For a Helm-Chart using these containers have a look at: puppetlabs/puppetserver-helm-chart
see RELEASE.md
see CONTRIBUTING.md