airbyte-cron-fips

packaged by Chainguard

Chainguard Container for airbyte-cron-fips

FIPS 140-3 variants of the six core Airbyte data-integration services. BCFIPS 2.1 is loaded as the JCE provider; conscrypt, netty-tcnative, and non-FIPS Bouncy Castle jars are stripped from the runtime.

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-cron-fips: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-fips image group provides FIPS 140-3 variants of the six upstream backend images that make up an Airbyte v2 deployment. Each Chainguard image is a drop-in replacement for its upstream counterpart, running under a FIPS-compliant JVM policy:

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

APM and OpenTelemetry agents

Each image ships /app/dd-java-agent.jar (Datadog APM) and /app/opentelemetry-javaagent.jar (OpenTelemetry Java Instrumentation), symlinked into /app for every service by the -compat subpackage. Both agents bundle their own HTTP/TLS clients that operate outside Bouncy Castle FIPS. If you enable either via JAVA_TOOL_OPTIONS (-javaagent:/app/dd-java-agent.jar or -javaagent:/app/opentelemetry-javaagent.jar), TLS from those agents will NOT route through BCFIPS, and outbound telemetry traffic will not be FIPS-validated. Do not enable them in an environment that requires end-to-end BCFIPS coverage.

Getting Started

Customers deploy this image group through the upstream airbyte/airbyte umbrella chart, overriding each component's image to the FIPS variant. 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-fips
    tag: latest
server:
  image:
    repository: cgr.dev/ORGANIZATION/airbyte-server-fips
    tag: latest
worker:
  image:
    repository: cgr.dev/ORGANIZATION/airbyte-worker-fips
    tag: latest
cron:
  image:
    repository: cgr.dev/ORGANIZATION/airbyte-cron-fips
    tag: latest
workload-api-server:
  image:
    repository: cgr.dev/ORGANIZATION/airbyte-workload-api-server-fips
    tag: latest
workload-launcher:
  image:
    repository: cgr.dev/ORGANIZATION/airbyte-workload-launcher-fips
    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 with every core component running on the Chainguard FIPS 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

FIPS Support

Each daemon runs on top of the Chainguard bcfips-policy-140-3-j21 policy. BouncyCastleFipsProvider and BouncyCastleJsseProvider are registered ahead of the JDK's default SunJSSE and SunJCE providers, non-FIPS Bouncy Castle modules (bcprov-jdk18on, bcpkix-jdk18on) are stripped from the classpath, and grpc-netty-shaded is forced to skip its embedded BoringSSL via -Dio.grpc.netty.shaded.io.netty.handler.ssl.noOpenSsl=true.

Confirm BCFIPS is active by inspecting one of the daemon's registered security providers. BCJSSE is only registered when the Bouncy Castle FIPS module is on the module path, so pass --module-path alongside -XshowSettings:security:

kubectl exec -n airbyte deployment/airbyte-server -- \
  java --module-path=/usr/share/java/bouncycastle-fips \
       -XshowSettings:security -version 2>&1 | grep -E 'BCFIPS|BCJSSE'

You should see BCFIPS and BCJSSE listed, and no SunJSSE or SunJCE:

BCFIPS version 2.1
BCJSSE version 2.0

Documentation and Resources

• Airbyte Deployment Documentation
• Airbyte Helm Chart Reference
• Airbyte Public API Reference
• Bouncy Castle FIPS 140-3 Java Certificate

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.