On Microsoft Azure, Krossboard is available as ready-to-use virtual machine images. This release approach makes its deployment as simple than creating a virtual machine.
Once deployed, the Krossboard instance is able to automatically discover and handle your AKS clusters. By default, the discovery works on a per Azure resource group basis, meaning that the instance does automatically discover and handle all your AKS clusters belonging to the resource group in which it’s deployed.
This guide shows how to setup Krossboard for a given Azure resource group. It’ll take you a couple of minutes to make it up and running.
This installation guide assumes that:
bash >=4terminal (or Azure Cloud Shell) where you can use Azure CLI.
kubectlinstalled and accessible from your terminal.
Open a terminal and perform the following commands to sign in to Azure and export variables required during the installation.
az login export AZURE_TENANT_ID=$(az account show --query "tenantId" | cut -d'"' -f2) export AZURE_SUBSCRIPTION_ID=$(az account show --query id | cut -d'"' -f2) echo "AZURE_TENANT_ID => $AZURE_TENANT_ID" echo "AZURE_SUBSCRIPTION_ID => $AZURE_SUBSCRIPTION_ID"
Azure requires that you consent to use a Image gallery from a third party.
Open a web browser and point it to the following URL. Change
$AZURE_TENANT_ID with your tenant ID (see the above steps).
Verify that the application is
krossboard-gallery-app, then check
Consent on behalf of your organization and click Accept.
The commands below shall deploy an instance of Krossboard in a couple of minutes.
Before running the commands, review and set the following variables suitably:
AZURE_GROUPsets the name of the resource group in which your AKS clusters are located.
KB_AZURE_VM_NAMEsets the name of the instance (default is automatically generated).
KB_AZURE_LOCATIONsets the deployment location (default is
centralus– see the list of regions with available images).
KB_AZURE_VM_SIZEsets the VM size (default is
--generate-ssh-keysof Azure CLI, meaning that it uses the local SSH key pair for the instance. The associated SSH username is
# deployment parameters export AZURE_GROUP="YOUR_AZURE_GROUP_WITH_AKS" export KB_AZURE_VM_NAME="krossboard-`date +%F-%s`" export KB_AZURE_VM_SIZE='Standard_B1ms' export KB_AZURE_LOCATION='centralus' curl -so krossboard_azure_install.sh \ https://raw.githubusercontent.com/2-alchemists/krossboard/master/tooling/setup/krossboard_azure_install.sh && \ bash ./krossboard_azure_install.sh
On success a summary of the installation shall be displayed as below:
=== Summary the Krossboard instance === Instance Name => krossboard-2020-08-18-1595880565 Resource Group => prod Krossboard UI => http://126.96.36.199/
Open a browser tab and point it to the Krossboard URL displayed at the end of the installation script.
The IP address of the instance is displayed at the end of the installation script. You can also get it on the Azure portal.
It may take a few seconds before the instance finishes its initialization, during this time you may experience a loading error in the browser.
Here are the default username and password to sign in:
It’s highly recommended to change this default password as soon as possible.
In case of problem, first checkout the Troubleshooting Page for an initial investigation.
If the problem you’re experiencing is not listed there, open a ticket on the Krossboard GitHub Page.
Alternatively, if you do have an active support contract, you can also send an email directly to our customer support service:
support at krossboard.app.
During the installation, the Krossboard deployment script discovers and takes over existing AKS clusters (in the same resource group). After the installation, you need apply the following change to enable RBAC access (read-only) to each new AKS cluster.
kubectl create -f https://raw.githubusercontent.com/2-alchemists/krossboard/master/tooling/setup/k8s/clusterrolebinding-aks.yml