Dash Enterprise Administration
4.3.1
4.3.1
  • Changelog
  • Installation
    • Capacity Planning
      • Dash Enterprise Single Server
      • Dash Enterprise for Kubernetes
    • Before you install
    • Dash Enterprise Single Server
      • Installation on cloud provider
      • On-premise installation on own server
      • Fully offline installation
    • Dash Enterprise Kubernetes
      • Amazon Web Services resource prerequisites
      • Google Cloud Platform resource prerequisites
      • Microsoft Azure resource prerequisites
  • Configuration
    • Set up your Server Manager
    • Run preflight checks
    • Configure basic settings
    • Authentication settings
      • Built-in local authentication
      • LDAP authentication
      • SAML authentication
    • Dash Enterprise Kubernetes additional required configuration
    • Configure optional settings
    • Add SELinux permissions to mapped directories
    • Other options and customizations
    • Using Snapshots & Backups
    • Running and logging into Dash Enterprise
    • Next steps
  • Advanced Configuration
    • General troubleshooting and problem solving
      • Dash Enterprise Kubernetes
    • Load balancer configuration
    • Reverse proxy setup instructions
    • Docker storage driver requirements and considerations
    • Import an LDAPS certificate from Active Directory into Dash Enterprise
    • Transfer Dash Enterprise to a new server
    • Sync license changes
    • Change channels for an upgrade
    • Admin panel reference
    • Configure Dash Enterprise to use common SAML IdPs
      • Active Directory Federation Services (AD FS)
      • PingFederate
      • Okta
    • Configure Dash Enterprise to use common LDAP IdPs
      • Okta
  • Upgrade
    • Prepare for the upgrade
    • Upgrade
      • Dash Enterprise Single Server
      • Dash Enterprise for Kubernetes
    • After the upgrade
  • Advanced Troubleshooting
    • Dash Enterprise Architecture and Internals
    • Navigating the System
    • Navigating the Support Bundle
    • Getting Help and Reporting Issues
    • Troubleshooting Specific Issues
Powered by GitBook
On this page

Was this helpful?

  1. Installation
  2. Dash Enterprise Kubernetes

Microsoft Azure resource prerequisites

PreviousGoogle Cloud Platform resource prerequisitesNextSet up your Server Manager

Last updated 2 years ago

Was this helpful?

  1. Create a Resource Group () to hold all the resources you will create in steps 2 through 5

  2. Create an Azure Linux virtual machine () with Dash Enterprise installed on it according to our instructions in . This instance will act as the Replicated Management Node.

    1. In the Networking section, set NIC network security group to advanced and add inbound ports as described in

    2. In the Management section, enable System assigned managed identity

  3. Create an Azure Database for PostgreSQL () instance using Postgres 11 and configure as follows:

    1. In Connection Security:

      1. Set Allow access to Azure services to Yes and add the IP address of the VM you created in Step 2 to the field

      2. Set Enforce SSL connection to Disabled

      3. Under Allow access to Azure services, add the IP address of your workstation, then connect to the Postgres instance and create the following two databases:

        • dashauth

        • dash_deployment_server

  4. Create an Azure Cache for Redis () and unblock port 6379

  5. Create an Azure Kubernetes Service cluster () and configure it as follows:

    1. Kubernetes version: choose the latest supported version from .

    2. Recommended node size: D4_v3

      1. Set this to N12s_v2 if the cluster will be used to deploy RAPIDS apps

    3. Node count: >= 4

    4. Authentication method: System-assigned managed identity

    5. Network configuration: advanced

      1. Use the same virtual network as the resource group

    6. Select Calico network services

    7. In the Integrations section, create a new container registry

  6. Assign the virtual machine from Step 2 the Contributor IAM role to the cluster as well as the container registry ():

    1. Go to the cluster’s page, select Add a role assignment from IAM roles and select the created VM as a Contributor

    2. Go to the container registry’s page and add the role assignment following similar steps

As part of installation, Azure will create a new resource group with the following naming structure:

MC_{resource group from step 1}_{cluster name}_{region}

To avoid configuration problems, do not modify this group.

guide
guide
Dash Enterprise Single Server: On-Premise Installation on Own Server
guide
guide
guide
guide
supported Kubernetes versions
Open ports