airbyte-workload-api-server

packaged by Chainguard

Chainguard Container for airbyte-workload-api-server

Minimalist images for the six core Airbyte data-integration services: bootloader (DB migrations + seed), server (REST/public API), worker (sync executor), cron (scheduler), workload-api-server (workload queue), and workload-launcher (dataplane daemon).

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/airbyte-workload-api-server:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

The airbyte-platform image group is comparable to the six upstream backend images that make up an Airbyte v2 deployment. Each Chainguard image is a drop-in replacement for its upstream counterpart:

Switching from the upstream airbyte/* images to the Chainguard versions should not require any changes to your existing setup — deploy them through the standard airbyte/airbyte umbrella Helm chart.

Getting Started

Customers deploy this image group through the upstream airbyte/airbyte umbrella chart, overriding each component's image to point at the Chainguard registry. Add the upstream Helm repository:

helm repo add airbyte https://airbytehq.github.io/helm-charts
helm repo update

Create a values file that overrides all six images:

cat > values.yaml <<EOF
airbyte-bootloader:
  image:
    repository: cgr.dev/ORGANIZATION/airbyte-bootloader
    tag: latest
server:
  image:
    repository: cgr.dev/ORGANIZATION/airbyte-server
    tag: latest
worker:
  image:
    repository: cgr.dev/ORGANIZATION/airbyte-worker
    tag: latest
cron:
  image:
    repository: cgr.dev/ORGANIZATION/airbyte-cron
    tag: latest
workload-api-server:
  image:
    repository: cgr.dev/ORGANIZATION/airbyte-workload-api-server
    tag: latest
workload-launcher:
  image:
    repository: cgr.dev/ORGANIZATION/airbyte-workload-launcher
    tag: latest
EOF

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Install the chart into a new namespace:

helm install airbyte airbyte/airbyte \
  --namespace airbyte \
  --create-namespace \
  --values values.yaml

Helm will deploy the full Airbyte stack — bootloader, server, worker, workload launcher, workload API server, cron, database, and Temporal — with every core component running on Chainguard images. Wait for the bootloader to finish and each daemon to come up:

kubectl wait --for=jsonpath='{.status.phase}'=Succeeded -n airbyte \
  pod/airbyte-airbyte-bootloader --timeout=10m
for d in server worker cron workload-api-server workload-launcher; do
  kubectl rollout status -n airbyte deployment/airbyte-$d --timeout=10m
done

Confirm the platform is healthy by hitting the server's anonymous health endpoint through a port-forward:

kubectl port-forward -n airbyte svc/airbyte-airbyte-server-svc 8001:8001 &
curl -sf http://localhost:8001/api/v1/health

{"available":true}

Documentation and Resources

• Airbyte Deployment Documentation
• Airbyte Helm Chart Reference
• Airbyte Public API Reference

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.