Skip to main content
Version: 1.38

Configure your Azure Cloud Resources

Azure requires multiple resources for Deeploy to operate successfully.

The complete Deeploy cloud setup is available in the Azure Marketplace. This is by far the easiest way to set up Deeploy.

GPU support

For GPU support we recommend attaching an autoscaling node group with your preferred GPU node type that can scale to 0 to your AKS cluster. Alternatively use Karpenter as a flexible scheduler. To make sure no other pods will be scheduled on GPU nodes you can add the following taint to your node pool:

taints:
- key: nvidia.com/gpu
value: present
effect: NoSchedule

When specifying a GPU node for a Deeploy deployment, automatically the nvidia.com/gpu label will be applied. To make sure you can select the nodes that are scaled to 0 in Deeploy, add a list of node types to the values.yaml file when you install the Deeploy Helm chart.

Firewall configuration

Important

This step needs to be completed for both Azure Marketplace and Azure CLI configurations

To ensure that the cluster nodes can access the Azure PostgreSQL database, the final step involves specific actions based on the database tier being used:

  • For the Basic tier, it is not possible to whitelist the Virtual Network (VNet) where the nodes are located. In this case, a firewall rule needs to be created on the DB server that whitelists the IP range encompassing all IPs of the AKS cluster nodes. The following steps need to be taken:
    • Obtain the IP range from the VNet of the AKS cluster nodes.
    • Add the Service Endpoint created above as a firewall rule on the DB server.
  • For higher tiers, it is recommended to create a VNet rule on the DB server that allows access from the subnet the AKS nodes are in. The following steps need to be taken:
    • Create a Microsoft.Sql Service Endpoint in the VNet of the AKS cluster nodes.
    • Add the Service Endpoint created above as a firewall rule on the DB server.