To configure r10k in an existing PE installation, set r10k
parameters in the console. You can also adjust r10k settings in
the console.
Before you begin
Ensure that you have a Puppetfile and a control
repository. You also need the SSH private key that you created when you made your control
repository.
-
In the console, set the following parameters in the
puppet_enterprise::profile::master
class in the PE Master node group:
-
r10k_remote
This is the location of your control repository. Enter a string that is a
valid URL for your Git control repository,
such as
"git@<YOUR.GIT.SERVER.COM>:puppet/control.git"
.
-
r10k_private_key
This is the path to the private key that permits the
pe-puppet
user to access your Git repositories. This file must be located on
the primary server, owned by the pe-puppet
user, and in a
directory that the pe-puppet
user has permission to view.
We recommend
/etc/puppetlabs/puppetserver/ssh/id-control_repo.rsa
.
Enter a string, such as
"/etc/puppetlabs/puppetserver/ssh/id-control_repo.rsa"
.
-
Run Puppet on your primary server and
compilers.
Results
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.