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
  1. Self-Hosting Pipekit

Container Images

Container Images

Last updated 9 months ago

The Pipekit installation consists of several container images, each of which is responsible for a different part of the Pipekit service. This page documents the images and their respective repository:

Image Repository
Image Name
Public or Private?
Required?
Reason image is optional

pipekit13

cli

Public

No

pipekit13

pipekit-agent

Public

Yes

pipekitprivate

events-handler

Private

No

Only required if you .

pipekitprivate

id

Private

Yes

pipekitprivate

messenger

Private

Yes

pipekitprivate

pipekit-init

Private

Yes

pipekitprivate

ui

Private

Yes

pipekitprivate

users

Private

Yes

In addition to the images listed above, the Pipekit installation also requires the following third-party image:

Image Repository
Image Name
Public or Private?
Required?

fluent

fluent-bit

Public

Yes

There may be additional images required for the installation, depending on how you choose to configure your .

Private Images

You will require a Docker Hub account with access to the pipekitprivate repository to pull the private images. This will be provided to you as part of your Pipekit subscription. Please contact us at for more information.

You will be permitted to attach a single Docker Hub account to the pipekitprivate repository. We recommend that you use this account to pull the images onto your own managed repository.

third party dependencies
hello@pipekit.io
integrate Pipekit with a git provider
Used for accessing the Pipekit CLI in a container