LogoLogo
PipekitPricingBlogPipekit StatusRelease Notes
  • Introduction
  • Getting Started
  • CLI
    • Cron Workflows
  • Pipekit Agent
    • Helm Install
  • Pipekit
    • Authentication
      • Okta
    • Runs
    • Pipes
      • Managing Pipes
        • Run Conditions
        • Secrets
        • Alerting
      • Pipe Runs
        • Run Graph (DAG)
        • Pod Logs
        • Workflow Logs
        • Workflow YAML
      • Cron Workflows
      • Externally Triggered Workflows
    • Metrics
    • Templates
    • Clusters
    • Organization
      • Creating an Organization
      • Managing Users
      • Managing Alert Providers
      • Settings
      • Permissions
  • Python SDK
    • Jupyter Notebooks
    • Python Scripts
  • Self-Hosting Pipekit
    • Dependencies and Pre-requisites
    • Container Images
    • Kubernetes Permissions
    • Self-Hosted Pipekit Helm Chart
    • License Key
    • Initial Login and Break Glass Account
    • Integrating with your Git Provider
    • Configuring SSO
  • Additional Information
    • Free Trial Cluster
  • REST API
Powered by GitBook
On this page

Pipekit Agent

About the Pipekit Agent

Last updated 1 year ago

The Pipekit Agent is a small application that runs within your Kubernetes cluster. It acts as the conduit to Pipekit's API, allowing you to run Argo Workflows from your local machine or through a Git repository.

The Pipekit Agent triggers Argo Workflows based on the configuration you set in Pipekit. It also sends the status of the Argo Workflow back to Pipekit, allowing you to see the status of your workflows in the Pipekit UI. Optionally, the Pipekit Agent can also send the logs of your Argo Workflows to Pipekit.

Pipekit Agent Software Bill of Materials (SBOM)

An SBOM for the Pipekit Agent is embedded within the container image in SPDX format. Further information is available on the page.

SBOM