Azure Automated Deployment Feature Guide

You can leverage the guided installation method for an automated Azure deployment and successfully install a worker node configured with your specifications. This enables customers to independently handle the worker node installation without needing the required technical understanding for worker node infrastructure deployment and install, which promotes a simpler onboarding experience and reduces implementation time.

To create the worker node

On the Data Discovery menu, select Setup > Worker Nodes. The Worker Nodes screen appears.
Click the Add Worker Node button. The Create Worker Node modal appears.
Complete the fields for the worker node details.
Select the Guided Install option, then choose Create From New.

Note:
For more information on worker node owners and email alerts, see Managing Email Notifications for Worker Nodes.
Click the Next button. The Platform Provider and Credential Store screen appears.
In the Platform Provider field, choose Azure.
The Automate Infrastructure Deployment field will default to Yes.
Choose your preferred sizing for the worker node: Small(5), Medium(15), and Large(40).

Tip:
If a large number of data sources or volume needs to be scanned, consider using a large-sized worker node.
Complete the remaining fields for the storage, namespace name, and chosen credential store.

Note:
For more information on support and configuration of credential vaults, see Credential Vault Options for Data Sources.
Click the Next button. The Advanced Options screen appears.
Configure the worker node with your desired advanced settings.

Note:
For more information, see Advanced Options in the Guided Installation Overview.
Click the Next button. The Set up a PIN screen appears.
Create and confirm a PIN for accessing the worker node installer file.
Click the Save button. The Worker Details screen appears.
Click the Launch Install button. The Launch Install modal appears.
Copy the following token for later use in the Azure portal. This string contains the worker node ID, URL, bearer token for authentication, worker node sizing, and namespace.

Important:
Please note these tokens expire after 1 hour.
Optional: A command is available in the Worker Details screen to download the installer and run additional scripts. This appears after installation.
Click the Launch in Azure button. A new browser window for the Azure portal will appear.

Note:
You may be prompted to sign in.

To launch install from Azure

Note:

You will need contributor access to the given resource groups and administrator access to run the installation script on the cluster. Click here for more information on these roles.

Contributor
User Access Administrator

In the Project details, confirm the subscription and resource group. Your resource group selection will populate the Region field in the Instance details section.
In the OneTrust Details, enter your PIN in the Worker Node PIN field.
The Virtual Network Details portion is optional.
Note:
By default, the automated ARM-based worker node uses a default VNet and Subnet CIDR, which may not align with your internal network configuration. If you are deploying into an existing Virtual Network (VNet), follow these steps:
Important:
Things to Know
- Ensure the selected VNet and Subnet do not conflict with existing network CIDRs.
- If your organization has strict network security policies, ensure outbound internet access is configured.
1. Under Virtual Network Details, select "Yes" for Select VNET for AKS Deployment.
2. Choose an existing Virtual Network for AKS from the dropdown.
3. Select a Subnet for AKS Cluster Deployment from the dropdown.
4. If you do not want to use a VNet, select "No", and a new VNet will be created automatically.
Click the Review + create button. The deployment will begin validating and post a status.
If you encounter a validation error, you may not have the necessary authorization to install the ARM Template on the specified Resource Group.
Once the validation is passed, click the Create button. The deployment will begin initializing and display the identified cluster(s) and deployment script. This may take a few minutes to complete.
If you encounter deployment errors, check the logs from Operation Details or click the HelmScript to troubleshoot.
If your deployment is complete but the worker node is not healthy, this may happen because some of the pods may not be ready. You can check the output of the script by searching in Azure for DeploymentWorkerNodeScript-<namespace> and open the resource. Click on the output to verify all pods are ready.