Jan
v3.1-38¶
13 Feb, 2026
Inventory Management¶
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.
Kubernetes Inventory¶
Inventory now supports automatic synchronization of Kubernetes nodes using a platform-recognized node-level label. Nodes labeled with paas.envmgmt.io/node-sync=true are automatically added as server devices in Inventory, with hardware details such as CPU, memory, storage, and GPU configuration populated dynamically.
This enhancement supports Pod-as-a-Service and GPU-based SKUs, including fractional GPUs using NVIDIA MIG, and ensures that inventory records remain continuously updated as node characteristics change.
SKU Management: Sharing and Visibility Controls¶
SKU Management has been significant enhanced in this release to provide additional controls to manage how SKUs are shared with tenant organizations and projects, and how SKU visibility is handled at a per-tenant level.
Sharing Behavior
| Org Scope | Auto-share | Behavior |
|---|---|---|
| All Orgs | True | SKU is shared with all tenant orgs and all projects within each org |
| All | False | SKU is shared with all tenant orgs, but not automatically shared with their projects. Tenant admins control project-level sharing. |
| Org-X | True | SKU is shared with Org-X and all projects in the Org |
| Org-Y | False | SKU is shared with Org-Y, but not automatically shared with projects |
SKU Sharing with Projects¶
When Operators share SKUs with specific tenant Orgs, they can now control whether the SKUs should be automatically shared with "all projects" in the tenant orgs or not. When the SKU is shared with a tenant org, the admin is now provided an option to "Share with All Projects".
In the example below, the SKU is shared with the Coke Org, but it is not automatically shared with "All Projects".
This means end users in the Coke Org will not automatically be able to consume the SKU until the Tenant Admin for the Coke Org explicitly shares the SKU with specific projects.
When Operators share a SKU with a tenant Org, they can also select the option to "Share with All Projects". When this option is selected, in the Coke Org, the tenant admin can see that the SKU in their Org is "already shared" with all projects. This means all users will now be able to consume the SKUs.
Org Exceptions for SKU Sharing¶
When sharing a SKU with "All Orgs", providers can now specify "exceptions" for Orgs. The SKU will not be automatically shared with the selected org exceptions.
Share SKU with All Projects¶
When sharing a SKU with "All Orgs", providers can now ensure that the SKU is made available to users in "All Projects" in customer tenant Orgs.
Per-Tenant SKU Visibility Control¶
Per-SKU, per-tenant configuration allows disabling a SKU for specific tenant organizations. When disabled, the SKU is hidden from the selected tenant organization and cannot be used for new instances.
Info
Existing instances created using the SKU are not impacted and remain available.
System Variables¶
In certain scenarios, specific variables need to be overridden through global settings (e.g. each tenant gets a dedicated cluster on which their applications are deployed). To support this, variables can be marked as system variables when creating a SKU/Profile in the SKU Studio.
System variables are visible only within the Default Org and are never exposed to tenant customers, ensuring a clean and consistent tenant experience. Marking a variable as a system variable also eliminates the need to explicitly mark it as overrideable when it must be controlled via global settings, as was previously required.
Centralized Blueprint Management¶
Blueprints enable assembling the required set of add-ons and applications (for example, GPU Operator and security software) that are installed during Kubernetes cluster provisioning. Previously, a Blueprint object had to be created within each tenant Org where a cluster was provisioned. With this release, providers can create Blueprint objects in their default Org and reference or consume them when provisioning clusters in tenant Orgs.
Usage Dashboard in Developer Hub¶
Similar to the tenant-level usage dashboard previously introduced for the tenant admin persona, this release adds an end-user usage dashboard.
Upon logging in, users can view a bird’s-eye summary of usage information based on their access, including:
- Number of workspaces
- Number of instances
- GPUs and CPUs allocated to instances
- An aggregated view of current resource utilization
This dashboard enables users to further drill down into specific details and take relevant actions as needed.
Ops Console Improvements¶
The following enhancements have been introduced in this release:
User Password¶
During organization creation, setting a user password is no longer required when SMTP is already configured on the Rafay Control Plane/controller. The user will be sent a temporary password to their email address and will need to use it to reset their password to their Org.
Read Only Roles¶
Support has been added for read-only roles, including Super Admin (Read-Only) and Partner Admin (Read-Only).
SMTP Configuration¶
In addition to the declarative YAML spec based approach that is already supported, SMTP configuration for the Rafay Control Plane can now be performed via the Ops Console.
User LCM Audit Logs¶
Audit logging has been enhanced for User Lifecycle Management (LCM) operations to improve visibility across partner and organization contexts.
Audit logs are generated for key user-initiated administrative actions and include partner and organization association, structured audit records stored in JSON format with expandable details, and filter support by operation type, user, client, and time range.
For more details, see User LCM Audits.
Resource-Level Deployment Status Messages¶
Compute and service instances now support resource-level deployment status messages sourced from annotations configured in resource templates. These annotations are defined per resource and are evaluated during instance deployment. When configured, the corresponding custom message is displayed on the instance page based on the current deployment state of each resource.
If no custom annotations are configured, the system continues to display the default environment-generated message.
Supported deployment states include In Progress, Success, Failed, and Waiting for Approval.
For more information, refer to Deployment Status Messages.
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.
Default Languages¶
English, Turkish, Japanese localization is supported by default.
Default Locale¶
Admins can specify the default locale for all users spanning all tenant orgs. The user will be presented with the language from the configured default locale.
Enable Language Selection¶
Admins can enable/disable language selection for users. When enabled, users will be provided the option to select from a list of available languages.
Administration¶
Admins can select/configure "language customizations" section as shown below.
Shown below is an example of the administrator adding language customizations for "Mandarin"
Info
In the same Rafay Controller, different languages can be supported for different partners. For example, Partner-Alpha may support English and Turkish. Partner-Beta may support Japanese and Turkish.
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.