1 Release 2.4.0 #
This release builds on the 2.3.x line with new partner blueprints, new SUSE AI applications in the catalog, and unique default namespaces for new installations, plus fixes for secret references on the Settings page, large Git-hosted charts and extension access checks.
1.1 What’s new #
New partner blueprints: The SUSE partner blueprint catalog now includes blueprints from three partners:
AlchemiStudio + vLLM(Zentience Labs),Tensormesh Platform on SUSE AI (vLLM)(Tensormesh), andTraefik Hub AI and MCP Gateway InstallerandTraefik Hub AI and MCP Governance Demo(Traefik Labs). Support for each blueprint is provided by its partner. Large partner charts such as AlchemiStudio now install from Git chart repositories #348.New SUSE AI applications:
vLLM Production Stack, which supersedes the existing vLLM application, plusSlurm OperatorandSlurm Bridgefor running Slurm alongside Kubernetes #357.NVIDIA catalog refresh: The weekly NVIDIA AI Enterprise catalog refreshes are included.
DOCA Weave Service(dpf-weave) is added to the NVIDIA AI Library #335, #350, #358.Random default namespace for new installations: The application and blueprint installation wizards now suggest a namespace with a random suffix, such as
coredns-k3x9q2a, instead ofcoredns-system. Each new installation gets its own namespace, so installing the same application twice no longer fails because a deployment with the same name already exists in the shared namespace. You can still change the namespace, and existing installations keep theirs #338.Incomplete secret references are caught before saving: on the Settings page is now blocked when a secret field has a secret selected but no key. The message names each such field and opens its section. The operator API rejects these partial references with HTTP
400, and the CRDs reject them from any client #349.
1.2 Key fixes #
Setting the SUSE Application Collection, SUSE Registry or NVIDIA credentials, or the Rancher Prime catalog token and CA certificate secrets, to
Nonenow saves. Previously, the page reloaded with the old credentials filled in, or saving failed with errors such asspec.applicationCollection.tokenSecretRef.name: Required value. This also happened when the reference was set by Helm values or discovered by the operator #349.Clearing every field of a section on the Settings page no longer fails with
spec.rancherCatalog in body must be of type object#349.Secret fields of custom repositories no longer silently drop a secret that has no key. Previously, saving appeared to succeed but stored
None#349.Charts from Git chart repositories that are larger than 1 MiB unpacked now install. Previously, they failed with
ChartTooLargeoretcdserver: request is too large. Chart files are now stored compressed, so a 2 MB chart takes about 0.43 MB #348.Global administrators are no longer refused access to the UI extension on their first navigation, for example, right after creating a cluster, with the message
Access check failed. The extension now waits up to 30 seconds for Rancher Prime to load its management data before checking access, and a failed check is retried on the next navigation #302.
1.3 Upgrade notes #
Updated
SettingsandInstallAIExtensionCRDs: Thenameandkeyof secret references must not be empty, and thefleet,applicationCollection,suseRegistry,nvidia,appCatalogandrancherCatalogsections ofSettingsacceptnull. The CRD hook job of the chart applies the CRDs on upgrade #349.Existing partial secret references: On Kubernetes 1.30 and later, a
Settingsresource that already stores a secret reference without a key, or a key without a secret, can still be updated as long as that field is not changed. Complete or clear these references the next time you edit the settings #349.Use matching operator and UI extension versions: The fixes for
Noneand partial secret references change both the operator API and the Settings page, and require both the 2.4.0 operator and the 2.4.0 UI extension #349.New default namespace pattern: New installations get a
<APP>-<RANDOM>namespace instead of<APP>-system. If your scripts or policies expect<APP>-system, set the namespace explicitly in the installation wizard. The action still finds instances installed in the earlier<APP>-systemnamespace #338.
1.4 Known issues and limitations #
Charts from Git chart repositories are limited to a 4 MiB archive, 32 MiB unpacked and 1 MiB of compressed files in the Fleet
Bundle.Non-administrator users get access to the UI extension through a
cluster-ownerrole binding for their user on thelocalcluster. Users who are cluster owners only through a group, for example, an LDAP group or a GitHub organization, are refused access.The vLLM application is superseded by
vLLM Production Stackand will be deprecated in a future release.
Full Changelog: aif-operator-2.3.1…aif-operator-2.4.0