Jazz Library IBM Engineering Air Gap Utility: Enabling Operator Deployments in Air-Gapped Environments
Author name

Introduction

The modern enterprise lives in a paradox. Cloud-native platforms such as Red Hat® OpenShift®, IBM Cloud® Kubernetes Service, and other Kubernetes-based container platforms are designed to retrieve container images, operator bundles, and catalog updates from external registries. However, many organizations in industries such as defence, banking, healthcare, government, energy — operate networks that are deliberately isolated from the public internet.

This is the air-gapped environment: a deployment model where systems operate in a full or partial isolated network with no direct internet access. Every resource a cluster needs container images, operator bundles, dependencies, catalog metadata — must be pre-downloaded and made available through an internal, private registry before a single workload can run.

Cloud-native meets physical isolation, Workflows that normally depend on external registries such as IBM container registries and Operator Lifecycle Manager (OLM) catalogs, must be redirected to internally hosted and mirrored content. This requirement introduces additional operational complexity and requires a structured approach to content preparation and management. This is not a configuration tweak — it is a fundamentally different operational model.

Operator Content Challenges

Preparing IBM CloudPak operator content for an air-gapped environment extends beyond downloading container images. Operator content consists of container images, CASE bundles, catalogs, and metadata that must remain consistent throughout the preparation, validation, transfer, and publication lifecycle.

  • No native bulk image transport  –  Operators can reference hundreds of container images across multiple public registries, and there is no built-in mechanism to collect and transfer them across a secured network boundary.
  • Catalog metadata hard-codes public paths – OLM catalogs contain image references that point to public registries. These references must be updated to use mirrored content in a private registry.
  • Multi-tool complexity – A complete mirroring workflow can involve tools such as skopeo, opm, Docker or Podman, and yq each with its own authentication and version requirements.
  • Security & Compliance Validation – Organizations often perform malware, vulnerability, and compliance scanning before content is introduced into the disconnected environment.
  • High upgrade overhead – New product releases typically require repeating the mirroring process to ensure that updated content is available in the disconnected environment.

The gap isn’t just in the network. It’s in the operational process — every disconnected deployment is a bespoke, error-prone manual endeavour without the right tooling.

The IBM Engineering Air Gap Utility

The IBM Engineering Air Gap Utility (AGU) is an interactive, menu-driven CLI framework that automates the disconnected content lifecycle for IBM CloudPak Operator solutions. It orchestrates the acquisition, transformation, packaging, and publication of container artifacts required for air-gapped environments.

The air-gap problem is a logistics problem, not a software problem. The images exist. The catalog metadata exists. The tools to move them exist. What is missing is an orchestration layer that automates the entire content lifecycle — from public registry to air-gapped private registry — in a repeatable, validated, product-aware way.

AGU provides a standardized workflow for disconnected content preparation by enabling:

  • Validate environment prerequisites.
  • Process IBM CASE bundles.
  • Mirror container images from supported registries.
  • Rebuild Operator catalogs with private registry mappings.
  • Package transferable artifacts for disconnected environments.
  • Publish rebuilt Operator catalogs to private registries.

AGU provides a standardized content preparation workflow while allowing organizations to perform security and compliance validation before transferring approved artifacts into the disconnected environment and publishing them to private registries.

Customer Benefits

By standardizing the disconnected content lifecycle, AGU helps organizations prepare and maintain air-gapped environments more efficiently.

  • Accelerated Onboarding – Reduces the time required to prepare operator content for disconnected environments.
  • Operational Consistency – Provides a repeatable workflow that reduces variability across environments.
  • Reduced Manual Effort – Minimizes manual artifact preparation, lowering the risk of configuration errors.
  • Simplified Lifecycle Management – Streamlines updates as new operator and CASE releases become available.
  • Enterprise Scalability – Supports standardized air-gap preparation across multiple CloudPak solutions and environments.
  • Improved Compliance Readiness – Helps organizations maintain controlled software distribution within secure, isolated networks.

Conclusion

As cloud-native platforms continue to evolve, operating in disconnected environments requires more than simply transferring container images — it demands a reliable process for preparing an entire software supply chain for air-gapped consumption.

The IBM Engineering Air Gap Utility (AGU) provides that missing orchestration layer. By transforming a traditionally manual and fragmented process into a standardized, repeatable workflow, AGU enables organizations to prepare operator content with greater consistency, scalability, and operational efficiency. The result is a streamlined path to delivering IBM CloudPak Operator solutions into secure, disconnected environments while allowing existing Kubernetes and Operator Lifecycle Manager (OLM) workflows to operate as intended.

Supported IBM Engineering Products

  • IBM Engineering Lifecycle Management on Hybrid Cloud
  • IBM Engineering AI Hub
  • IBM Rhapsody Systems Engineering

Getting Started

To get started with the IBM Engineering Air Gap Utility (AGU), download the utility from the Jazz.net and refer to the README for setup instructions, supported products, and usage guidance.


Tue, 28 Jul 2026