Release notes for IBM App Connect Operator 12.3.0
Review these release notes for information about supported versions, new features and enhancements, and known issues and workarounds.
Version information
This release relates to IBM App Connect Operator 12.3.0.
The support requirements for the IBM App Connect Operator 12.3.0 are as follows:
Option | Supported requirement |
---|---|
Deployment platforms |
|
Certified container | Based on IBM App Connect Enterprise certified container 12.3.0 |
Image | Contains an image of IBM App Connect Enterprise 12.0.12.5 |
Installation |
|
This documentation relates to the release for these listed versions. Documentation for the previous releases of the Operator is available in PDF format at Documentation for previous releases.
New features and enhancements
- Support for a new IBM App Connect Operator channel, and custom resource (or operand) channels or versions
-
IBM App Connect Operator 12.3.0 is delivered on a new
v12.3
Operator channel, which you must select to install 12.3.0 versions of the Operator, or to initialize an upgrade from a 12.2.1 or earlier Operator.Accompanying versions and licenses are provided for the App Connect Dashboard, App Connect Designer Authoring, Switch Server, Integration Server, and Integration Runtime custom resources (or operands). To create an instance or upgrade to a 12.3.0-specific version of a custom resource (CR), you must choose both of these options:- Subscribe to the
12.0
or12.0.12
channel for custom resources, or specify a fully qualified version of12.0.12.5-r1
. - Select a 12.3.0-specific license for approval.
- Subscribe to the
- Ongoing support for Red Hat OpenShift Container Platform 4.12, 4.14, 4.15, and 4.16
-
IBM App Connect Operator 12.3.0 supports Red Hat OpenShift 4.12, 4.14, 4.15, and 4.16, but on a 4.16 cluster, you can create App Connect Dashboard, App Connect Designer, switch server, integration server, and integration runtime instances at version
12.0.12.4-r1
or later only. Similarly, if you upgrade your cluster to Red Hat OpenShift 4.16, you must upgrade all your existing instances to version12.0.12.4-r1
or later.More information: - Renamed connector in App Connect Designer and App Connect Dashboard
-
The Apptio Targetprocess connector has been renamed to IBM Targetprocess.
More information:- App Connect Designer: Supported components for flows
- App Connect Dashboard: Supported components for export
- How-to guides for apps
- Default affinity rules added for an integration runtime
-
Default affinity settings are now defined for an integration runtime. The default spec.template.spec.affinity.nodeAffinity and spec.template.spec.affinity.podAntiAffinity settings allow the integration runtime pod to be placed on a supported platform and, where possible, spread the replicas across hosts. You can overwrite the default settings with custom affinity settings.
More information: Integration runtime: Custom resource values
Deprecated or removed features
- Deprecated operand versions and channels
-
A number of operand versions and channels are deprecated for the IBM App Connect Operator 12.3.0 and might no longer be reconciled by future versions of the Operator. A deprecation notice is displayed if you try to save a new or existing Dashboard, Designer, switch server, integration server, or integration runtime custom resource if its spec.version value resolves to a deprecated version.
More information: spec.version values
- Removed operand channels and versions
-
The following operand versions, which were deprecated in IBM App Connect Operator 12.1.2, are removed from IBM App Connect Operator 12.3.0:
- 12.0.12-r2
- 12.0.12.3-r1-lts
After you upgrade to version 12.3.0 of the Operator, existing App Connect Designer, App Connect Dashboard, switch server, integration server, or integration runtime instances that resolve to a removed version are no longer supported and cannot be reconciled by the Operator.
- You can upgrade the instance to a supported version by updating the spec.version value and accepting the appropriate license.
- You can delete the instance if it's no longer required.
- You cannot save modifications to the custom resource settings if the instance is at an
unsupported version. If you require an instance at a version that is unsupported in Operator 12.3.0,
you must install an Operator version from the
v12.2
or earlier channel, and then create an instance at the version that you require.
More information: