Add a local runner to the Kubiya platform to deploy actions to & use those from within workflows
Local runners are currently supported only from within Kubernetes
You'll need a Kubernetes cluster in order to setup a local runner

Action Runners

Action runners are a fundamental component of Kubiya, enabling you to execute action stores on your own infrastructure. With action runners, you can leverage the power of Kubiya SDK and execute your custom actions in a scalable and flexible manner.

Key Features

Action runners offer several key features that enhance the capabilities of Kubiya:
  1. 1.
    Custom Logic Execution: Action runners allow you to execute your custom logic, enabling you to build and execute actions tailored to your specific needs.
  2. 2.
    Local Network Access: Action runners enable execution of actions within local networks, such as virtual private clouds (VPCs), even when external network access is restricted. This allows you to leverage Kubiya's functionality while maintaining a secure network environment.
  3. 3.
    Full Control: With action runners, you have full control over the source code of your actions. You can manage your own repositories, enabling seamless development and deployment workflows for your custom actions.
  4. 4.
    Self-Hosted integrations: Kubiya supports self-hosted action stores, which empower you to create custom actions using the Kubiya SDK. These action stores can be hosted locally on a Kubernetes cluster, providing a powerful and flexible solution for executing serverless functions against supported infrastructures.

Getting Started

To get started with action runners, you need to set up the runner infrastructure on your own Kubernetes-based infrastructure. The installation process can be done using Kubernetes Manifest, Kind, or Minikube. Each method has its own advantages, and you can choose the one that best fits your requirements:
From the web interface
From the Slack App
  1. 1.
    Go to the Kubiya web interface "Action Runners" page:
Click on "Add Action Runner":
  1. 1.
    Name your runner: usually, the prefed naming convetion would be the place it is running from. eg. "staging" or "dev":
  1. 4.
    Select the deployment method of the runner: currently, only Kubernetes is available as an orchestrator:
  1. 5.
    Copy the generated URL to your cliboard:
  1. 6.
    Paste the kubectl command in the command line - make sure you are running from the desired context or use --context <context>
  2. 7.
    Done! The runner deployment is now set and you can deploy integrations to it!
  1. 1.
    Go to slack to your Kubi app
  2. 2.
    Execute the /manage command
  3. 3.
    Hit on Create Local Runner
  1. 4.
    Hit on Deploy New Runner
  1. 5.
    Provide a meaningful name (could be the name of the cluster/environment/purpose)
  1. 6.
    Copy the command and execute it within your kubernetes cluster
  1. 7.
    Hit the Connect button and you will have Kubiya being able execute actions in your own environment ready for your order