Deploy with a bash script to a single node kubeadm cluster

Applies to: SQL Server 2019 (15.x)


The Microsoft SQL Server 2019 Big Data Clusters add-on will be retired. Support for SQL Server 2019 Big Data Clusters will end on February 28, 2025. All existing users of SQL Server 2019 with Software Assurance will be fully supported on the platform and the software will continue to be maintained through SQL Server cumulative updates until that time. For more information, see the announcement blog post and Big data options on the Microsoft SQL Server platform.

In this tutorial, you use a sample bash deployment script to deploy a single node Kubernetes cluster using kubeadm and a SQL Server big data cluster on it.


  • A vanilla Ubuntu 20.04 server virtual or physical machine. All dependencies are set up by the script, and you run the script from within the VM.


    Using Azure Linux VMs is not yet supported.

  • VM should have at least 8 CPUs, 64-GB RAM, and 100 GB of disk space. After pulling all big data cluster Docker images, you will be left with 50 GB for data and logs to use across all components.

  • Update existing packages using commands below to ensure that the OS image is up-to-date.

    sudo apt update && sudo apt upgrade -y
    sudo systemctl reboot
  1. Use static memory configuration for the virtual machine. For example, in Hyper-V installations do not use dynamic memory allocation but instead allocate the recommended 64 GB or higher.

  2. Use checkpoint or snapshot capability in your hyper visor so that you can roll back the virtual machine to a clean state.

Instructions to deploy SQL Server big data cluster

  1. Download the script on the VM you are planning to use for the deployment.

    curl --output
  2. Make the script executable with the following command.

    chmod +x
  3. Run the script (make sure you are running with sudo)

    sudo ./

    When prompted, provide your input for the password to use for the following external endpoints: controller, SQL Server master, and gateway. The password should be sufficiently complex based on existing rules for SQL Server password. The controller username defaults to admin.

  4. Set up an alias for the azdata tool.

    source ~/.bashrc
  5. Refresh alias setup for azdata.

    azdata --version


The script is provided as convenience to reset the environment if necessary. However, we recommend that you use a virtual machine for testing purposes and use the snapshot capability in your hypervisor to roll back the virtual machine to a clean state.

Next step