Azure Marketplace Deployment

This guide walks you through deploying LightBeam from the Azure Marketplace after purchase.

Installing LightBeam from Azure Marketplace

This includes filing out some basic profile information to submit to Microsoft to install the application.

1. Visit the LightBeam Azure listing

2. Click on "Get it Now" and complete the profile information

1. Select "LightBeam Software Package" plan and click "Create"

Azure Deployment Configuration

Basics

• Subscription: Select your Azure subscription

• Resource Group: Choose existing or create new (must be empty)

• Region: Select Azure region for deployment

JumpVM Setup

• VM Name: Name for your JumpVM

• Size: Choose from supported sizes:

  • Standard_DS1_v2

  • Standard_DS2_v2

  • Standard_DS3_v2

  • Standard_B1s

• Username: JumpVM login username

• Authentication: Choose SSH Public Key or Password

• Access IP: Specify allowed IP range in CIDR format:

  • Corporate network: e.g., 10.0.0.0/16

  • Single user: your IP with /32 (e.g., 203.0.113.1/32)

  • Avoid using 0.0.0.0/0 for production environments

LightBeam Cluster Configuration

• LightBeam Version: Software version to deploy

• Network: Choose new or existing Azure VNET (/16) and Subnet (/20)

• AKS Cluster Name: Default or custom name

• Node Pool VM Size: Choose from supported sizes:

  • Standard_D8s_v3

• Node Count: Number of nodes (contact [email protected] for sizing recommendations)

• Setup Token: Obtain from [email protected] after purchase

• License Key: Obtain from [email protected] after purchase

Complete the configuration, review, and click "Create".

Deployment takes approximately 40 minutes.

Accessing LightBeam

After the LightBeam cluster is installed, use the below instructions to access the LightBeam Web Interface.

Connect to JumpVM

1. Find JumpVM's public IP in Azure Portal

2. SSH into JumpVM:

# For password authentication:
ssh username@public_IP

# For SSH key authentication:
chmod 400 your_key_file
ssh -i your_key_file username@public_IP

Get LightBeam Web UI Information

1. Switch to root on JumpVM:

sudo su

1. Get the web UI address:

kubectl get ingress -n lightbeam -o jsonpath='{.items[0].status.loadBalancer.ingress[0].ip}' && echo

1. Retrieve admin password:

kubectl exec deploy/lightbeam-api-gateway -- printenv 2>/dev/null | grep AUTH_PASSWORD | awk -F= '{print $2}'

1. Access LightBeam at http://<obtained_IP> using:

• Username: admin

• Password: <retrieved_password>

Troubleshooting

Connect to JumpVM as described above and check these log files:

• Main handler log:

cat /var/log/azure/custom-script/handler.log

This is the primary log file for the Azure VM extension that runs custom scripts during deployment. It records overall extension execution status, including when scripts start and finish, and any high-level errors.

• Deployment stdout/stderr:

cat /var/lib/waagent/custom-script/download/0/stdout
cat /var/lib/waagent/custom-script/download/0/stderr

These files contain the actual console output from the deployment scripts:

1. stdout shows the normal output of commands that ran successfully

2. stderr captures error messages and warnings from failed commands

These logs provide detailed information about what specific commands were executed and their results during the initial setup process.

• Terraform and AKS deployment logs:

cat /root/lightbeam/lightbeam-tf-iac/aks/terraform_apply.log

This log specifically focuses on the infrastructure deployment stage using Terraform. It shows:

1. AKS (Azure Kubernetes Service) cluster creation

2. Node pool configuration and deployment

• LightBeam application deployment logs:

cat /root/lightbeam/lightbeam-chart/lightbeam_install.log

This final log shows the deployment of the actual LightBeam application into the Kubernetes cluster.

Uninstallation

1. Connect to JumpVM and switch to root:

sudo su

1. Clean up LightBeam cluster:

cd /root/lightbeam/lightbeam-chart
./installer/lb-cleanup.sh

1. Remove AKS infrastructure:

cd /root/lightbeam/lightbeam-tf-iac/aks
terraform destroy

Type "yes" when prompted and wait for completion

1. Complete cleanup:

• Delete all resources from the Azure Resource Group

  • Network Security Group,Network Interface, Jump VM Public IP, VNET, Subnet, JumpVM etc.

• Remove JumpVM role assignments (Network Contributor and AKS Service Contributor)