Upcoming
Important
This page will be periodically updated with features that are scheduled to roll into Rafay's Preview environment as part of upcoming releases. Learn more about Previews. Learn about our recent releases.
Navigate to our public roadmap for details on what we are working on for future releases.
v3.0 - SaaS¶
Expected rollout date: December 11, 2024 for Production Orgs
Catalog for System Templates¶
System Catalog¶
With this, the platform will offer a catalog of pre-built system templates designed to simplify and enhance the user experience for administrators. These templates are fully supported by Rafay, with regular updates and new features added over time.
With the system templates, Rafay Admins have to follow two simple steps to provide a self service experience for their end users:
- Share the system template from the system-catalog project to other project(s).
- Configure, customize and publish the system template (i.e. provide credentials, specify defaults and determine what values end users can/cannot override)
Info
Administrators can also use the published system template with instance and service profiles in the newly introduced PaaS to provide end users with a self service experience.
The system catalog will significantly improves the process of consuming capabilities available in the platform.
Key Features:
-
Shareable Templates: Organization Administrators can share the catalog templates with specific projects, enabling the creation of environment instances based on them
-
Customizable: Users can clone and customize catalog templates to align with their unique workflows. For example, adding a ServiceNow approval step before initiating an environment provisioning
System Templates¶
The following templates are available with this release. Additional system templates will be made available progressively along with incremental updates to the existing templates.
Cluster Lifecycle
| # | Template Name | Description |
|---|---|---|
| 1 | system-gke | Configure, Templatize and Provision GKE clusters using GCPs' native IaC Provider |
| 2 | system-mks | Configure, Tempalatize and Provision a Kubernetes Cluster (Rafay MKS) on any supported OS |
| 3 | system-vsphere-mks | Configure, Tempalatize and Provision a Kubernetes Cluster (Rafay MKS) on VMware vSphere |
Multi-Tenancy
| # | Template Name | Description |
|---|---|---|
| 1 | system-vcluster-anyk8s | Self Service Provisioning of a vCluster on a shared host cluster with integrated multi-tenancy controls |
AI/ML
| # | Template Name | Description |
|---|---|---|
| 1 | system-kuberay-anyk8s | 1-Click, self-service provisioning of a Ray as a Service environment for Data Scientists and ML Researchers |
| 2 | system-mks-kubeflow | 1-Click Deployment of Rafay's Kubeflow based MLOps Platform on a Rafay MKS Cluster |
| 3 | system-gpuoperator-mks | 1-Click Deployment of the Nvidia GPU Operator on a Rafay MKS Cluster |
Note
The templates are designed to support both Day 0 (initial setup) and Day 2 (ongoing management and maintenance) operations.
For more information on this feature , please refer here
Environment Manager¶
Drivers (aka Workflow Handlers)¶
A previous release added the ability to execute code written in Go or Python via:
- Resource templates through the Custom Provider option
- Hooks attached to the resource/environment template configuration (e.g. Approval is need in ServiceNow before an environment provisioning is initiated)
- Schedule policies (e.g. capture snapshot of K8s resources every 24 hrs)
Configuration options for the same was made available via RCTL CLI, Terraform, System Sync and APIs interfaces with the previous release. Support for UI interface is now being added.
GPU Platform as a Service (GPU PaaS)¶
The primary objective of Rafay's GPU PaaS offering is to empower GPU Cloud providers and enterprise customers to deliver GPU self-service capabilities to their end users. To facilitate this, two additional portals are available:
-
PaaS Studio: Designed for administrators to create and manage pre-defined configurations (profiles), such as GPU compute, that can be made accessible to end users.
-
Developer Hub: Intended for end users to log in and launch instances based on the pre-defined profiles for their consumption.
Note
These additional portals are, by default, accessible only to Organization Admins. Non-Org Admin users must be explicitly assigned a role to gain access to these portals.
For more information on this feature , please refer here