Jan
Info
GPU PaaS releases are initially rolled out via Rafay's Air Gapped Controller form factor. These will be periodically bundled and rolled out into Rafay's Production SaaS.
v3.1-38¶
09 Jan, 2026 (est.)
Inventory: Bulk Node Onboarding¶
For VM as a Service SKUs, admins now have access to a "bulk node onboard" workflow to manage their server inventory. This allows admins to onboard 10s or 100s of servers at the same time enabling providers to add capacity quickly and efficiently.
Inventory: MIG Support¶
Fractional GPUs based on Nvidia MIG are now supported natively in the inventory.
Inventory: Kubernetes Cluster¶
Inventory based on Kubernetes clusters will be automatically reconciled and kept updated based on current usage on clusters.
SKU Mgmt: Configurable Controls for SKUs¶
We have introduced configurable automation and policy controls for how SKUs are shared with tenant orgs and projects within these orgs.
Controls¶
| Setting | Description |
|---|---|
| Share With Specific Org | SKU is available to specified tenant org only |
| Share With All Projects | SKU is made available to all projects within each org |
Behavior Matrix¶
| Org Scope | Auto Share with All Projects | Result / Behavior |
|---|---|---|
| All | True | SKU is shared with all tenant orgs and all projects within each org |
| All | False | SKU is shared with all orgs, but not automatically shared with their projects. The tenant admin controls project-level sharing. |
| Tenant-X | True | SKU is shared with tenant-x and all projects within that tenant. |
| Tenant-Y | False | SKU is shared with tenant-y, but not automatically shared with its projects. |
SKU Mgmt: Per SKU, Per Tenant Configuration¶
When a SKU is shared with all tenant orgs, it is currently not possible to hide it from a specific org.
In this release, we have introduced a "per-SKU" & "per-Tenant" configuration to disable a SKU in an Org. When enabled, the tenant org will no longer see the SKU/profile
Info
Existing instances based on the SKU will not be impacted and can still be viewed or used.
SKU Studio¶
The PaaS Studio portal used by admins to design and manage SKUs has been renamed as "SKU Studio".
- Only GPU Cloud Providers (not their end customers) will have access to this portal.
- PaaS Admin & Org Admin in the provider's "Default Org" will have access to SKU Studio.
New Org Type¶
Service Providers can now create Orgs with the type "CSP". For users in these orgs, the Infra and SKU Studio portals are not available/visible.
Managed Kubernetes¶
Control plane and worker nodes can now be provisioned on RHEL 10 and Flatcar Linux.
Managed Kubernetes Versions¶
Support for new cluster provisioning of Kubernetes v1.33 and v1.34. Existing k8s clusters can be upgraded in-place to these versions. The default k8s version with this release is v1.33
Info
k8s v1.34 brings support for DRA. Read our blogs about this new feature for GPUs
External Storage for Controller¶
During installation of the self hosted/air gapped controller, admins can now specify a CSI provider for external storage managed by the organization. For example, the organization may have standardized on a storage platform such as Vast or DDN or Weka or Ceph. This is the recommended and required option for production deployments.
Info
The default "openebs" based CSI option is still available, but limited to only POCs and Demos.
Internationalization & Localization¶
The end user facing self service portal can now be localized to support different languages via language resource bundle files provided via the Ops Console.
Adminstration¶
Admins can perform this by selecting the "language customizations" section as shown below.
Shown below is an example of the administrator adding language customizations for "Mandarin"
End User Experience¶
End users can select their preferred language when they login into the self service portal. Shown below is an example when the user selects Japanese as their preferred language in the login page.
Once the user logs in, the self service portal is shown using the Japanese language customizations.
The user is also shown the selected language customizations when they try to launch/consume SKUs. In the example below, the user has selected "Turkish" as their preferred language.
Info
As of this release, we support only left-to-right languages, with additional language support planned for the future.