|Index|SUSE AI Factory Release Notes|Release 2.2.0

4 Release 2.2.0

This release builds on the 2.1.x line with enhanced support for air-gapped deployments, recovery operations for blueprint workloads, an NVIDIA AI Enterprise application catalog that is generated and refreshed automatically, and a range of reliability fixes in the operator’s Helm lifecycle.

4.1 What’s new

4.1.1 Application catalog

  • Generated NVIDIA AI Enterprise catalog: The NVIDIA AI Library is generated from the NVIDIA GPU Cloud (NGC) catalog and gated on NVIDIA AI Enterprise support, replacing the previously hand-maintained label refresh #223.

  • Automated catalog refresh: A scheduled job regenerates the catalog weekly, so the Supported labels on NVIDIA applications stay current between releases #232.

  • NGC repository classification: NGC repository paths are classified as organization, public, gated or excluded. Gated repositories are provisioned with the authentication secret, and unrecognized paths fall back to anonymous access #223.

  • NGC image pull secret injection: NVIDIA charts receive the ngc-secret image pull secret under both supported chart value conventions, which resolves 403 errors caused by an empty default suppressing the injection #223.

  • Catalog scoped to managed repositories: The Apps page lists applications only from ClusterRepo resources that SUSE AI Factory created. Previously, an unrelated ClusterRepo could add applications to the SUSE AI or NVIDIA libraries #182.

4.1.2 Air-gapped deployments

  • Private chart and Git sources: Blueprints reference a chart repository by its identity, while the registry endpoints in Settings determine where that repository is hosted. The same blueprints therefore deploy unchanged against a local mirror. Private HTTPS Git is supported for both blueprint input and GitOps output #224.

  • Private CA certificate propagation: You can select a CA certificate secret for SUSE Application Collection, SUSE Registry and NVIDIA in Settings. The operator propagates it to Rancher Prime and Fleet, and handles CA certificate and credential rotation #200.

  • NVIDIA blueprint repository in mirrored mode: Both the NVIDIA application and NVIDIA blueprint repository identities are preserved when mirrored and pointed at your private OCI URL, so NVIDIA blueprints continue to resolve #201.

  • Image registry override: A single global.imageRegistry value redirects every image shipped by the operator and UI extension charts #209.

4.1.3 Workload recovery

  • Upgrade, roll back and retry: Blueprint workloads can be upgraded to a new blueprint version, rolled back, or retried after a failed deployment directly from the UI. Application workloads do not support these operations #214.

  • Verified rollback target: A blueprint version becomes a rollback target only after it has been fully rolled out across all target clusters, so a workload cannot be rolled back to a version that never reached a healthy state #214.

  • Per-component and per-pod status: Workloads report their status for each component and pod, including while a deployment is failing, which makes it easier to identify the component that is blocking the rollout #214.

4.1.4 Usability improvements

  • Open workloads in Rancher Prime: Each workload row provides an Open in Rancher action that opens the corresponding Helm release or namespace, with a cluster selector for multi-cluster workloads #206.

  • Library filter is preserved: Cancelling an application installation returns you to the library you were browsing, and filtered catalog views can be bookmarked and shared #215.

  • Catalog metadata for the UI extension: The extension is listed as SUSE AI Factory with the correct metadata in the Rancher Prime Apps and Marketplace views #230.

  • Clearer confirmation dialogs: The upgrade and rollback confirmation dialogs explain the effect of the operation #229.

4.1.5 Packaging

  • CRD lifecycle: CRDs are installed natively on first installation, and a hook job applies schema upgrades. The new crds.rbac.create and crds.serviceAccountName values support restricted environments where the installer cannot create cluster-scoped RBAC #202.

  • Per-component Helm release names: Blueprint components accept an optional releaseName value that pins the Helm release name of a component. It defaults to the chart name #202.

  • UI extension installed by the operator: The operator installs the UI extension itself, so aif-ui is no longer installed as a separate Helm chart #233.

4.2 Key fixes

  • Restarting the operator no longer leaves the UI extension’s Helm release in a failed state without recovering #199.

  • The UI extension no longer remains on an incorrect version after consecutive upgrades and downgrades #177.

  • Deleting an application workload now uninstalls the underlying Helm chart instead of leaving the release in the Uninstalling state with orphaned resources #193.

  • The operator no longer downloads the UI extension chart on every reconcile, which previously caused continuous registry traffic and could exhaust public registry rate limits #185.

  • Attaching image pull secrets no longer removes other service account fields, such as labels, annotations, owner references and finalizers #192.

  • Several user interface strings and tooltips that previously displayed raw translation keys now render correctly #211.

  • Long Helm release names no longer prevent the UI extension from installing. The generated service name could exceed the Kubernetes 63-character limit and be rejected #210.

4.3 Upgrade notes

  • CRDs are retained on uninstall: helm uninstall no longer removes CRDs or the Settings resource. Bundled blueprints and the UI extension are still removed. Schema upgrades are applied by a pre-install and pre-upgrade hook job #202.

  • Mirror the kubectl image for air-gapped installations, because the CRD hook job requires it. Alternatively, set crds.manageWithJob=false and apply the CRDs manually with kubectl apply --server-side -f crds/ before each upgrade #202.

  • The UI extension is no longer installed separately: If your automation installs the aif-ui chart as a separate step, remove that step and the aiExtension.enabled: false override #233.

  • Deleting workloads outside the UI requires a Rancher Prime token: Deleting an AIWorkload resource with kubectl or through GitOps only uninstalls the chart when a token is configured in Settings > Rancher API Access. Without a token, the deletion is held rather than orphaning the Helm release #193.

  • Manually created chart repositories are ignored: Only ClusterRepo resources created by SUSE AI Factory contribute to the application catalog #182.

  • HTTPS Git authentication: The authentication type setting is deprecated, and existing configurations continue to work. For new authenticated HTTPS configurations, select a password or personal access token. The user name is optional unless the Git server requires an account name. SSH is not supported #224.

  • Unused settings were removed: The SUSE Application Collection API endpoint, catalog discovery and image rewrite settings, and the Advanced section of Settings were removed #224.

  • New workload validation: Review existing AIWorkload resources before upgrading. The deployment strategy is now immutable, blueprint workloads require at least one target cluster, and GitOps workloads cannot combine the local cluster with downstream clusters #214.

  • Image overrides for air-gapped installations: The global.imageRegistry and global.imagePullSecrets values of the aif-operator chart are now forwarded to the managed aif-ui chart. Existing nested overrides take precedence #209.

4.4 Known issues and limitations

  • Air-gap support covers private chart repositories, private Git repositories, repository credentials and CA trust. Preparing the cluster remains a separate task: node and containerd registry mirrors, DNS, host proxies and operating system repositories are not configured by SUSE AI Factory.

  • Container image references inside blueprint values are not rewritten. Your containerd registry mirrors must resolve them transparently.

  • Git over SSH is not supported. Use HTTPS with credentials and, where required, a private CA certificate.

  • Upgrade, rollback and retry apply to blueprint workloads only. A workload that has never reached a healthy, fully rolled out state has no rollback target.

Full Changelog: aif-operator-2.1.0…​aif-operator-2.2.0