Kubernetes on Azure
Context
The purpose of this document is to describe how to create the necessary infrastructure to deploy Vectice on a Kubernetes cluster in Azure, followed by instructions to deploy the Vectice software
Understanding prerequisites
Infrastructure requirements
#
Requirement
Notes or Details
1
Security Groups
Port 443 (HTTPS)
3128 Outbound (pip install)
SMTP Port (e.g 2525)
2
Kubernetes Cluster
v1.16+ deployed agentpool: 1 node Standard_D4s_v4
userpool: 2 nodes with Standard_D4as_v4
3
Azure Blob Storage Container
In the same region
4
Azure Database for PostgreSQL flexible server
13.x Cloud SQL instance
Other requirements
#
Requirement
Notes or Details
5
Domain Name
Example: https://vectice.my-company.com
6
SSL Certificate
Must be associated with the domain name above
Self-signed certificates are not recommended
Deployment environment with the following tools:
7
Helm v3
8
Kubectl
9
Azure CLI
11
Openssl
2. How to provision the infrastructure
You have two ways to create the infrastructure necessary for running Vectice.
Provisioning via Terraform (with Terragrunt Wrapper)
Expected Time: 40 minutes
Steps:
Provisioning via Azure portal
Expected Time: 2 hours
Steps:
Create a resource group in your chosen subscription
3. How to deploy the Vectice application
The provisioning of Vectice on Kubernetes will happen in 5 steps:
Step 1: Connect to the cluster and create the Vectice namespace
First, define the variables for the next steps and retrieve connections from your deployment machine. Below, sample values are provided between brackets:
The expected output should look like this:
Next, test the connection:
The expected output should look like this:
Finally, create the Vectice namespace where applications will be deployed:
Step 2: Install the Cert Manager
Next, install the cert-manager and cert-manager-csi-driver applications on the cluster.
Next, generate a custom Certificate Authority and create its associated secret:
Step 3: Set up the Application Gateway on the cluster
If you did not have an existing Application Gateway, the creation could be blocked because of a permission issue. The AG needs to create a subnet on the Vnet used by the AKS Cluster.
As the AG belongs to the Managed Resource Group of the AKS cluster, permission is needed to add on the Managed Identity of the AG.
Navigate to the AKS managed Resource group created along with the cluster and Click on the managed Identity that contains the name of your AG (it might take a few minutes to appear).
Navigate to the Azure role assignment menu, and add the role "Network Contributor" to the general resource group you use for the resources (not the AKS managed resource group).
Add root-certificate to the application gateway
Step 4: Create Secrets for Ingress and Docker Image Retriever
First, create a self-signed certificate using the following command, replacing the item highlighted with your own Common Name (CN). Below, sample values are provided between brackets.
Then, use the command below to install your certificates in the cluster
Step 5: Install the Vectice Stack
From the package your account team provided, untar helm vectice chart and create myvalues.yml
from values.yml
file. Below, sample values are provided between brackets.
Next, fill in the values in myvalues.yaml
according to your environment deployment, and deploy Vectice global objects using Helm
Once this is done, retrieve the Vectice ingress IP. Note: this might take up to 5 minutes to appear
The expected output should look like this. Below are example values:
Finally, add the A record as a new entry in your DNS resolver.
In this example, the A record would look like below:
Last updated
Was this helpful?