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.

Continuous Delivery release model

Continuous Delivery (CD) releases undergo continuous testing, integration, and deployment to rapidly 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.

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.

IBM App Connect Operator versions that are delivered on the CD release stream are supported on Red Hat® OpenShift® Container Platform or Kubernetes environments.

Long Term Support release model

Unlike CD releases, which incrementally add features or enhancements with each new release, Long Term Support (LTS) releases typically offer only fixes or security vulnerability updates in IBM App Connect Operator 5.0.x versions after the initial LTS release of 5.0.0. LTS releases also occasionally include deprecations or removals if an integrating application, service, or endpoint is deprecated or discontinued. Because LTS 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, LTS releases are also typically delivered at monthly intervals.

IBM App Connect Operator versions that are delivered on the LTS release stream are supported on Red Hat OpenShift Container Platform environments only.

Note:

LTS releases of Operator 5.0.x reach End of Support (EOS) at the end of 2024, but upgrade paths are supported from LTS 5.0.x to a CD release model, or from LTS 5.0.x to a Long Term Support Cycle-2 release model.

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 LTS releases and has similar characteristics. Like LTS, the SC2 model typically offers only fixes or security vulnerability updates in subsequent Operator versions after the initial release, and might occasionally include deprecations or removals due to discontinued services. SC2 releases also 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 documented for the Support Cycle lifecycle policy, the SC2 release model for the IBM App Connect Operator offers a two-year base support period (from the General Availability date) with options to purchase extended support.

IBM App Connect Operator versions that are delivered on the SC2 release stream are supported on Red Hat OpenShift Container Platform or Kubernetes environments.

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 IBM 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:

• Starting in June 2024, CD releases are assigned an initial Operator version of 12.1.0 and adopt a 12.x.0 numbering scheme in subsequent releases, where x increments by 1 in each subsequent release. Operator versions for previous CD releases are numbered 11.6.0 or earlier.
• LTS releases are assigned an initial Operator version of 5.0.0 and adopt a 5.0.x numbering scheme in subsequent releases, where x starts at 1.
• 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.

Operator versions are delivered on channels within a configured Red Hat OpenShift cluster or Kubernetes cluster (if supported for the release model). 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, together with the corresponding IBM App Connect Enterprise certified container versions, and their support requirements, see IBM App Connect Enterprise certified container versions.

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