Skip to content

Clone Templates

Compute and Service profiles are based on environment templates powered by Rafay's Environment Manager. We will be using Rafay's curated and pre-created system templates available from the catalog in our compute and service profiles. 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 Template

As an Org Admin, navigate to "System->Template Catalog". On the "Multi-tenancy on K8s" item/card,

  • Click on "Get Started" and follow the wizard
  • Provide a name, version and select the name of the project you created in the previous step (e.g. gpu-paas)
  • Save as Draft

Share Compute Template

Configure Compute Template

Specify Agent

The agent will receive the IaC, credentials and policies from the Rafay Platform and implement it on the behalf of the user.

  • Under the "Agents" tab, click on "Add Agent"
  • Select the name of the agent you configured in the prior step
  • Save your changes

Select Agent

Config Context

The config context will typically hold credentials and environment variables required for the agent to do its job.

Navigate to the menu item "Config Context" and click on "New"

API Key for Org

Create a new Env Variable with the following details

  • Key = RCTL_API_KEY
  • Value = Copy the API Key + Secret credentials

To get the API Key + Secret for programmatic access, navigate to "My Tools -> Manage Keys" and click on "New API Key".

Info

Click here to learn more about API Key & Secret for programmatic access.

  • Set the variable options as "sensitive" and overrides as "Not Allowed". This means that downstream end users will not see this or be able to manipulate it.

Controller API Endpoint

Create a new Env Variable with the following details

  • Key = RCTL_REST_ENDPOINT
  • Value = console.rafay.dev

Ensure you set override as "Not Allowed" because we do not want any downstream users of the template to see it or have access to it.

Important

Please replace "console.rafay.dev" with your customized URL if you have been setup for white labeling.

Once saved, the config context should look like the image below.

Config Context

Jupyter Notebook Template

Jupyter Notebooks are web based applications. When these are deployed on your cluster, they will be exposed to users via Kubernetes based Ingress. So, please ensure that you have a properly configured Ingress Controller in your host cluster by following the infrastructure related instructions. The Ingress for the notebook will be exposed via a https URL on a domain.

As an Org Admin, navigate to "System->Template Catalog". On the "Jupyter Notebook" item/card,

  • Click on "Get Started" and follow the wizard
  • Provide a name, version and select the name of the project you created in the previous step (e.g. gpu)
  • Save as Draft

Share Notebook Template

Info

To aid with testing and evaluation, the Rafay platform provides the option to automatically publish the DNS and inject a certificate for the https URL on a Rafay managed domain. We will use this option for our exercise.

Configure Notebook Template

Select Agent

The agent will receive the IaC, credentials and policies from the Rafay Platform and implement it on the behalf of the user.

  • Under the "Agents" tab, click on "Add Agent"
  • Select the name of the agent you configured in the prior step
  • Save your changes

Select Agent

Config Context

Add the previously created config context to the template.

  • Under the "Config Contexts" tab, click on "Add Config Context"
  • Select the name of the context you configured in previously
  • Save your changes

Select Context