Skip to content

Setup

In this exercise, you will then create a namespace and provision KEDA Helm chart within the namespace

Important

This tutorial describes the steps using the Rafay Web Console. The entire workflow can also be fully automated and embedded into an automation pipeline

Assumptions

You have already provisioned or imported a Kubernetes cluster into your Rafay Org.

Step 1: Create Namespace

  • Login into the Web Console
  • Navigate to Infrastructure -> Namespaces
  • Create a new namespace, specify the name (e.g. keda) and select type as Wizard
  • In the placement section, select a cluster
  • Click Save & Go to Publish
  • Publish the namespace

Create namespace

Step 2: Create KEDA Add-on

  • Navigate to Infrastructure -> Add-Ons
  • Select New Add-On -> Create New Add-On from Catalog
  • Search for keda
  • Select KEDA from default-helm

Catalog

  • Select Create Add-On
  • Specify the namespace (e.g. keda and select the host namespace created as part of the previous step

Addon create

  • Click Create
  • Enter a version name
  • Click Save Changes

keda create

Step 3: Create Blueprint

  • Navigate to Infrastructure -> Blueprints
  • Select New Blueprint
  • Enter a name for the blueprint
  • Click Save

Blueprint

  • Enter a version name
  • Click Configure Add-Ons
  • Select the previously created add-on
  • Click Save Changes

Blueprint

  • Click Save Changes

Blueprint

Step 4: Apply Blueprint

  • Navigate to Infrastructure -> Clusters
  • Click the gear icon on your cluster and select Update Blueprint
  • Select the previously created blueprint
  • Click Save and Publish

Blueprint

After a few seconds, the blueprint with the KEDA add-on will be published on the cluster.

Blueprint

Step 5: Verify deployment

  • Navigate to Infrastructure -> Clusters
  • Click KUBECTL on your cluster
  • Type the following command
kubectl get all -n keda

KEDA

Recap

Congratulations! You have successfully provisioned KEDA on your cluster using a blueprint. This same cluster blueprint can also be used on additional clusters.