Configure

The GPU NaaS template enables self service namespace creation within an existing shared host kubernetes cluster. The namespace comes preconfigured with a GPU instance with a predefined resource quota. The host cluster can be configured with full GPUs, MIG GPUs configured in a single strategy or timesliced GPUs. In this guide, we will be using Rafay's curated template for GPU NaaS available from the Template Catalog. The Org Admin for the user's Rafay Org has the privileges to share the system templates from Rafay's Catalog to specific/all projects.

• Compute profiles are based on environment templates powered by Rafay's Environment Manager.

Note that administrators can also create and configure Custom environment templates for use cases outside the list supported out of the box in Rafay's Template Catalog.

Configure Template

When the template is executed by the Rafay agent operating behind the firewall, it will receive the configured template, the associated Infra as Code (IaC), credentials and policies from the Rafay Platform. It will then execute this code on the behalf of the user.

1. Specify Agent

Let's configure the template to be received and executed by the Rafay Agent we created in a prior step.

• Under the "Agents" tab, click on "Add Agent"
• Select the name of the agent you configured in the prior step
• Ensure that the override configuration is specified to "Not Allowed" because we do not want the downstream users to be able to change this
• Save your changes

2. Config Context

The config context will typically encapsulate credentials and environment variables required for the agent to perform its job. In this case, we will configure the Rafay Agent with credentials so that it can make programmatic (API) calls to the Rafay controller.

To get the Rafay API Key for the administrator user,

• Navigate to "My Tools -> Manage Keys" and click on "New API Key".
• Copy the API Key + Secret combination.

Now, we are ready to configure our agent's config context.

• Under the "Config Contexts" tab in the environment template, edit "rafay-auth-config"
• Expand "Environment Variables" and you should see two entries: Host Cluster API Key & Controller Endpoint
• Click on Edit for Host Cluster API Key
• Paste the API Key/Secret string from the above step into the value section
• Select Override to "Not Allowed" to ensure none of the downstream users have visibility or access to the config context
• Save & Continue

Controller API Endpoint

For self hosted Rafay Controller deployments, the agent will need to be configured to point to its URL. In our Get Started Guide, we will be using the URL for Rafay's SaaS option.

• Click on Edit for Controller Endpoint

• Note that Rafay's SaaS Endpoint URL is already configured and can be updated if required

• Select Override to "Not Allowed" to ensure none of the downstream users have visibility or access to the config context

• Save & Continue

• Click Save

Configure PaaS

Next, we will configure a custom PaaS service profile to allow self service users to deploy the template.

• Navigate to PaaS Studio
• Select "Compute Profiles"
• Select the project where the template was previously created
• Click "New Compute Profile"
• Enter a name for the profile
• Select the previously created template and version
• Click Save & Continue

On the following screen, navigate to "Input Settings"

• Deselect "Allow Override For All" and then click "Deselect All". This will prevent the user from changing these settings.
• Select "Override" for "Namespace Quota Size"
• Update the input variable value for "Cluster Name". This is the host cluster where the GPU namespaces will be created.
• Navigate to "Output Settings"
• Click "Add Output"
• Enter the following outputs

• Click Save Changes

Next Step

At this time, the administrator is ready to open up this profile (SKU) for end users. Learn how end users can launch and use their GPU namespaces on Kubernetes.