Skip to content

Jul Patch 2

v3.1-40 Update 2

31 Jul, 2026

This update release primarily includes bug fixes and minor enhancements to existing features listed below.

Ops Console

Notifications

Operators can now configure notifications that are displayed to users in tenant organizations either on the login page, within the console after login, or in both locations. Notifications can include a title and rich-text or HTML content, along with defined start and end times that control when they are visible.

In-console notifications can be targeted to specific organizations or displayed to all organizations. Multiple in-console notifications can be active during overlapping time periods.

Login-page notifications are displayed to all organizations and cannot have overlapping visibility windows.

Create Notification

For tenant users, in-console notifications are displayed in a scrollable panel. After a notification is marked as read, the unread count is updated and the notification icon returns to its neutral state. The following example shows a notification displayed directly on the login page.

View Notification

GPU Cluster Blueprint

The GPU cluster blueprint has been updated with NVIDIA GPU Operator v26.3, which is compatible with Kubernetes v1.34.x, v1.35.x and v1.36.x. The default blueprint includes the NVIDIA GPU Operator and Management Operator components. GPU cloud operators can create custom blueprints to include additional add-ons, such as monitoring components, as needed.

Swagger Support

A previous release introduced support for configuring agents, quotas, variable overrides, and rate cards through the Ops Console. Swagger API documentation is now available for each of these capabilities.

Token Factory

Model Display Name

This enhancement allows operators to configure a "model display name" for model deployments which is then displayed to end users in the self service portal. End users can access/use the endpoints using the display name.

Model Display Name

Like in the image below, end users are shown both the actual and display name in their model cards. They can access the model using either the actual or display name.

End User Model Display Name

Playground

The integrated playground has been enhanced to support markdown formatting. This is particularly useful when users utilize code blocks in the playground.