Install applications via the PAM UI

The process of adding an application once you've installed Puppet Application Manager is simple.

Important: Ensure you are using the following Puppet application versions if you want to add more than one Puppet application via the Puppet Application Manager UI:
Application Version
Continuous Delivery for Puppet Enterprise 4.6.0 or later
Comply 1.0.4 or later

For information on installing Puppet applications via the command line, see Automate PAM and Puppet application online installations and Automate PAM and Puppet application offline installations.

To install a Puppet application using the Puppet Application Manager UI:

  1. Log into the Puppet Application Manager UI, and click Add a new application.
    • If you have not added a Puppet application before you are prompted to upload a license.

    • If you have already added a Puppet application, click Add a new application.

  2. Upload your replicated_license.yaml file when requested.
    Note: Once the license file is installed, if offline installations are enabled, you are presented with an option to proceed with an offline setup.

    Add the following information to install an offline application:

    • Hostname - the hostname you want to use to configure an Ingress and to tell job hardware agents and web hooks how to connect to it. You might need to configure your DNS to resolve the hostname to your Kubernetes hosts.
      Important: The hostname must be unique for each application you install.
    • Username/Password - The username and password for the application root account. The root account is used to administer your application and has full access to all resources and application-wide settings. This account must NOT be used for testing and deploying control repositories or modules.
    • Registry namespace - the registry namespace for the application, e.g. CD4PE or Comply.
    • Airgap bundle - upload the relevant application bundle tarball. Click Continue.
  3. Added any additional required information that is presented on the Config page. Configure any other settings on the page relevant to your installation, such as external databases, customized endpoints, a load balancer, or TLS certificates. Click Save Config when you are done.

    Saving your new configuration settings prompts the creation of a new application version.

  4. Click Go to new version, which redirects you to the Version history tab. The newly created version is shown in the All versions section of the page.
  5. Monitor the new version's preflight checks. The Running Checks indicator is shown on the screen while your system is checked to make sure your cluster meets minimum system requirements. When the preflight check is complete:
    • If the status is Checks Failed, click View preflights. Correct the issues and click Re-run. Repeat this step as needed.
      Important: Do not move on until all preflight checks pass.
    • If the status is Ready to Deploy, move on to the next step.
  6. Once the version is ready to deploy, click Deploy. On the Application tab, monitor the application for readiness.
    The application's status is shown as Missing for several minutes while deployment is underway. To monitor the deployment's progress, run kubectl get pods --watch.

    When the deployment is complete, the application status changes to Ready.

  7. Navigate to https://<HOSTNAME> (using the hostname you entered on the Config screen) and sign into your application.