Creating a Dedicated Compute Cluster for Azure
Important
From Kyvos 2025.4 onwards, the High Availability of Compute Server process for Dedicated compute cluster support has been added. This ensures continuous service availability and automatically recovers from unexpected downtimes.
In case of an existing deployment upgraded to version 2025.4, you must update the PostCreationDedicatedCompute script. Follow the case 2 as specified for all cloud platforms (AWS, Azure, and GCP), and delete the existing attached script.
You can create a dedicated compute cluster either by downloading the JSON file or manually creating a compute cluster.
Note
The resource group of the dedicated compute cluster must be the same as the Kyvos cluster deployment resource group.
Supported dedicated compute instance types
Dsv4 size series (recommended Standard D16s v4)
Disk Size (recommended 250GB)
CASE 1: By downloading the ‘DedicatedCompute_VMSS’ JSON file
Download the PostCreationDedicatedComputeAzure JSON file available in the Azure Installation Files folder.
Log in to Azure portal.
Search for ‘Deploy a custom template’ in the search bar.
Upload the downloaded JSON file.
Provide the same parameter that you mentioned while creating Kyvos cluster.
CASE 2: Manually creating a dedicated compute cluster
Go to Azure Portal.
Click On create a virtual Machine Scale Set (VMSS).
Select Subscription, Resource Group, and provide the Virtual Machine Scale Set name.
Orchestration mode for Dedicated Compute Cluster must be Uniform only.
Verify that the instance count must be 0.
From the Image drop-down, choose the supported RHEL version from the list.
Red Hat Enterprise Linux 8.6 - Gen 2 option (recommended).
Red Hat Enterprise Linux 9.4 - Gen 2
Red Hat Enterprise Linux 7.8 - Gen 1
Once the machine is created, you must attach the Managed Identity that is used for the deployment stack.
Add the following tags to the created VMSS.
ROLE: KYVOS_COMPUTE_CLUSTER
LAYER: Cube_Build
Download the Dedicated_Compute.sh script located in the Azure Installation Files folder.
In the script, update the blank parameters that required deployment-specific information.
Fill the information for those parameters.
Now, convert the script in base64 encryption.
Update the resource group name, VMSS name, and the script value in the command and then execute it.
az vmss extension set \ --resource-group <RESOURCE_GROUP_NAME> \ --vmss-name <VIRTUAL_MACHINE_SCALE_SET_NAME> \ --name CustomScript \ --publisher Microsoft.Azure.Extensions \ --no-auto-upgrade false \ --version 2.0 \ --settings '{"script":"<BASE_64_FORMAT_OF_SCRIPT>"}'
It will add extension to the VMSS and whenever any instance will launch, it will download the prerequisites on the instance.
NEXT:
Refer to the wizard-based deployment section for further details on deploying Kyvos.
For post deployment, see the Post-upgrade steps to configure external dedicated compute cluster section.