Configuring r10k
When performing a fresh text-mode installation of Puppet Enterprise (PE), you can configure r10k by adding parameters to the pe.conf
file. In existing installations, configure r10k by adjusting parameters in the
console.
Upgrading from previous versions of r10k
If you used r10k prior to
PE version 2015.3, you might have configured it in
the console using the pe_r10k
class. We
suggest configuring r10k in the master profile class, and
then customizing your configuration as needed in Hiera.
This simplifies configuration, and makes it easier to move to Code Manager in the future.
To switch to master profile class configuration, remove the
pe_r10k
class in the
console, and then configure r10k as described in
the topic about configuring r10k after PE installation. You can then customize your
configuration in Hiera if needed.
Note: If you were using earlier
versions of r10k with the zack-r10k
module, discontinue use of the module and
switch to the master profile configuration as above.
Configure r10k during installation
To set up r10k during PE installation, add the r10k
parameters to pe.conf
before
starting installation. This is the easiest way to set up r10k with a new PE
installation.
Ensure that you have a Puppetfile and a control repo. You also need the SSH private key that you created when you made your control repo.
Configure r10k after PE installation
To configure r10k in an existing PE, set r10k parameters in the console. You can also adjust r10k settings in the console.
You can now customize your r10k configuration in Hiera, if needed. After r10k is configured, you can deploy your environments from the command line. PE does not automatically run r10k at the end of installation.