Product Documentation

Appearance

VNet Architecture ​

Deploying this Partner Solution with default parameters builds the following Yellowbrick Cloud Data Warehouse Manager (CDWM) in the Azure Cloud.

The Yellowbrick Installer in Azure provides a range of options for VNet setup, from fully public to fully private:

  • Fully private: Installation into an existing VNet on a private network that the customer provides, given a list of prerequisites. This option is recommended for customers with enterprise security concerns. The installation process does not touch the customer's environment but installs into it and integrates with the existing network configuration.
  • Fully public: Installation into a new VNet on a public network with internet access. The installation process builds everything from scratch.

You can also install Yellowbrick with some other security options, including use of your own Blob storage for Yellowbrick data storage.

The following architecture diagram shows a private network installation in a hub-and-spoke environment, where the Yellowbrick software is deployed into a spoke VNet with its own private subnets.

The following architecture diagram shows a public network installation, with internet access.

As shown here, the Partner Solution sets up the following:

  • A highly available architecture that spans multiple availability zones (AZs).
  • A VNet configured with public and private subnets according to Azure best practices, to provide you with your own virtual network on Azure.

In the public subnets: Managed network load balancer(s) to allow outbound internet access for resources in the private subnets.

  • An Application Load Balancer attached to the public subnets. The load balancer directs traffic to the Cloud Data Warehouse Manager pod(s) configured as a Kubernetes ingress.

  • One or more Network Load Balancer(s) attached to the public subnets. Each load balancer directs traffic to each Cloud Data Warehouse instance configured as a Kubernetes service. In the private subnets: In the first availability zone, a primary Azure Kubernetes Service (AKS) node with application pods in an Auto Scaling resource group.

  • Three Azure Blob Storage (ABS) volumes for Cloud Data Warehouse Manager (CDWM).

  • Two Azure Blob Storage (ABS) volumes for each Data Warehouse instance’s block storage.

  • A private and encrypted Azure Blob Storage (ABS) for each Data Warehouse instance’s object storage.

  • Azure Kubernetes Service (AKS) for the cluster to run Cloud Data Warehouse Manager (CDWM) and Cloud Data Warehouse instances as containerized applications.

Parent topic:Azure Deployment Guide for Yellowbrick