Skip to main content

Enterprise Runner

Enterprise Runner

Available in PagerDuty Runbook Automation Commercial products.

Orchestrating Automation Across Disparate Environments

The Enterprise Runner allows for dispatching automation to remote environments that Runbook Automation can not reach directly.

This architecture allows for orchestrating various tasks and automation playbooks across multiple environments, including secure and remote environments.

The Runner is equipped with most of the same plugins Runbook Automation, making it easy to use the Runner with existing automation.

Tasks can be carried out over multiple environments simultaneously, thereby reducing the time and complexity of orchestrating automation across disparate environments.

Runner Architecture Overview

Runners Orchestrate Automation Across All Environment Types

  1. The Runner uses a polling model to pick up work from Process or Runbook Automation. During each polling cycle the Runner checks for executions that it is responsible for.
  2. Communication from the Runner to Runbook Automation happens over HTTPS and is initiated from the Runner. This implies that no inbound firewall ports need to be open for the Runner.
  3. Tasks come into the Runner's queue from users and tools that are interfacing with Runbook Automation.
  4. The Runner retrieves tasks from the response of queries to Runbook Automation and performs them in the remote environment.
  5. Output of the task is sent back to Runbook Automation for logging and reporting.
    • The output or result of the tasks can then be used to trigger subsequent tasks or workflows.
  6. The Runner can use secrets retrieved from a secrets provider that is not directly accessible from Runbook Automation.
    • Secrets retrieved this way stay within the Runner's environment and are not sent back to Runbook Automation.
  7. The Runner can use existing automation tools or communicate directly with infrastructure and APIs in the remote environment.
    • The Runner can be used to discover inventory in secure or remote environments.
  8. The Runner can be deployed as a container within Kubernetes clusters to perform actions within the cluster.

Enabling the Latest Runner Features

Enabled by Default for Docker and Runbook Automation SaaS

This feature has been enabled on Docker installations since v4.5.0 and is also enabled by default for Runbook Automation.
If using either Docker or Runbook Automation, the feature is enabled by default and no further action is required.

To use the latest Enterprise Runner features, the following feature-flags must be enabled in System Configuration or optionally in the rundeck-config.properties file if using the self-hosted software.

rundeck.feature.runner.enabled=true

rundeck.feature.distributedAutomation.enabled = true