Release models, packaging, and versions for the IBM App Connect Operator

Release models for the IBM App Connect Operator

The release models for the Operator have similar delivery frequencies, but differ in the type of content (functional, maintenance, or security updates) that they deliver. The Operator versions that are delivered for each release model are supported on Red Hat® OpenShift® and Kubernetes environments.

Continuous Delivery release model

The Continuous Delivery (CD) release model delivers new features, enhancements, fixes, and security vulnerability updates at monthly intervals. Fixes are provided only on the latest operand version of the IBM App Connect components or custom resources, so an upgrade to the latest operand version is required to obtain a fix.

CD releases are supported for a minimum of two years from the date when the product was made generally available by IBM, and options are available to purchase extended support.

Long Term Support Cycle-2 release model

The Long Term Support Cycle-2 (SC2) release model is a replacement for the IBM App Connect Operator 5.0.x Long Term Support (LTS) release, which reached End of Support (EOS) at the end of 2024. Unlike CD releases, which incrementally add features or enhancements with each new release, SC2 releases of IBM App Connect Operator 12.0.x typically offer only fixes or security vulnerability updates in subsequent Operator versions after the initial SC2 release of version 12.0.0. SC2 releases might also occasionally include deprecations or removals if an integrating application, service, or endpoint is deprecated or discontinued. Because SC2 releases offer minimal updates, they might be preferred for environments where a long-term deployment is desirable, but frequent functional updates are not practical. Similar to CD releases, SC2 releases have a monthly delivery schedule for fixpacks and you must upgrade to the latest operand version to obtain fixes for defects, or to keep up to date with monthly security fixes.

As indicated by the Support Cycle lifecycle policy for IBM software, the SC2 release model for the Operator offers a two-year base support period from the General Availability date. Options are then available to purchase extended or sustained support.

Long Term Support Cycle-3 release model

The Long Term Support Cycle-3 (SC3) release model is a replacement for both the CD and SC2 releases. Similar to CD releases, SC3 releases undergo continuous testing, integration, and deployment to deliver new features, enhancements, fixes, and security vulnerability updates at monthly intervals. Fixes are provided only on the latest operand version of the IBM App Connect components or custom resources, so you must upgrade to the latest operand version to obtain a fix.

As indicated by the Support Cycle lifecycle policy for IBM software, the SC3 release model for the Operator offers a three-year base support period from the General Availability date. Options are then available to purchase extended or sustained support.

For more information, see IBM Software Support Lifecycle Policies.

How the IBM App Connect Operator is packaged and versioned

Each IBM App Connect Operator version packages an IBM App Connect Enterprise certified container image that is built from an App Connect Enterprise version. Based on your requirements, you can install an IBM App Connect Operator version as part of an IBM Cloud Pak for Integration deployment or as an independent App Connect Enterprise certified container deployment. The following installation options are available:

• Installation in a cluster that is connected to the internet (with access to public registries where images are stored)
• Installation in a cluster that is not connected to the internet (that is, an air-gapped or restricted network environment)
  • On Red Hat OpenShift environments, this option provides a Container Application Software for Enterprises (CASE) bundle, which enables images to be mirrored to an internal registry.
  • On Kubernetes environments, this option provides a script that you can run to mirror the images to an internal registry.

IBM App Connect Operator version numbers are assigned by release model:

• Operator versions for the initial CD releases were numbered 11.6.0 or earlier. Starting in June 2024, a 12.x.y numbering scheme was reassigned to CD releases, where x starts at 1 and increments by 1 in subsequent releases, and y starts at 0 (zero). The Operator versions range from 12.1.0 (for the June 2024 release) to 12.21.0 (for the final release in February 2026).

  CD releases for Operator 12.1.0 to 12.3.0 are based on App Connect Enterprise 12, whereas CD releases for Operator 12.4.0 to 12.21.0 are based on App Connect Enterprise 13.

• SC2 releases start with an Operator version of 12.0.0 (in June 2024) and adopt a 12.0.x numbering scheme in subsequent releases, where x starts at 1 and increments by 1 in subsequent releases.

  SC2 releases for all Operator 12.0.x versions are based on App Connect Enterprise 12.

• SC3 releases start with an Operator version of 13.0.0 (in March 2026) and adopt a 13.x.y numbering scheme in subsequent releases, where x starts at 1 and y starts at 0 (zero).

  SC3 releases for all Operator 13.x.y versions are based on App Connect Enterprise 13.

  To support upgrade paths from a CD or an SC2 release to an SC3 release, a set of operand versions from the 12.21.0 CD Operator and the latest operand version from the latest 12.0.x SC2 Operator are included in each SC3 release.

Operator versions are delivered on channels within a configured Red Hat OpenShift cluster or Kubernetes cluster. Licensing for these Operator versions aligns with App Connect Enterprise licensing. For more information, see Licensing reference for IBM App Connect Operator.

Each Operator version also offers multiple custom resource or operand versions that you can use to create your App Connect authoring and runtime environments, as well as servers, within your Red Hat OpenShift or Kubernetes cluster. You can set the custom resource (or operand) version for an App Connect environment or server to a fully qualified version number, which indicates that an instance of that specific version should be created. You can alternatively set the version to a custom resource (or operand) channel, which indicates that the Operator should create the instance by using the latest fully qualified version in that channel. The specified version determines which container image is downloaded for the App Connect environment or server that is created, and the level of functionality that is available. For more information about how version numbers are resolved in channels, see spec.version values. For a summary of the features in each custom resource (or operand) version, see IBM App Connect operand versions and features.

IBM App Connect Operator versions and support requirements

To see the full set of available IBM App Connect Operator versions and their support requirements, see IBM App Connect Enterprise certified container versions.

For information about the Operator releases that have reached end of support, see IBM App Connect Enterprise certified container versions (end of service).