Local Hosting

Proxmox

Local hosting on a Proxmox VE host.

Proxmox Workshop Instance Setup #

Overview #

The ubuntu-cloud-k3d.sh script automates the creation of a Splunk Observability Workshop VM on Proxmox VE. It creates a complete Ubuntu 24.04 cloud-init based VM with all necessary tools and configurations pre-installed.

Prerequisites #

• Proxmox VE cluster with administrative access
• Internet connectivity for downloading cloud images and packages
• Available VM ID range and storage space
• Valid SWiPE ID for workshop access
• Snippets enabled on local storage - Required for cloud-init configuration files. To enable:
  1. In Proxmox web UI, go to Datacenter → Storage → local
  2. Click Edit
  3. Under Content, add Snippets to the list
  4. Click OK

Quick Start #

Run the script directly on your Proxmox host:

k3d script:

bash -c "$(curl -fsSL https://raw.githubusercontent.com/splunk/observability-workshop/refs/heads/main/local-hosting/proxmox/ubuntu-cloud-k3d.sh)"

k3s script (LEGACY):

bash -c "$(curl -fsSL https://raw.githubusercontent.com/splunk/observability-workshop/refs/heads/main/local-hosting/proxmox/ubuntu-cloud-k3s.sh)"

What the Script Does #

1. Initial Setup #

• Updates package repositories and installs required tools (jq, curl)
• Displays interactive prompts for user confirmation and SWiPE ID input

2. Authentication & Configuration #

• Validates SWiPE ID against the Splunk workshop API
• Retrieves workshop tokens and configuration (REALM, RUM_TOKEN, INGEST_TOKEN, etc.)
• Generates unique VM ID and hostname

3. VM Creation #

• Downloads Ubuntu 24.04 Noble cloud image
• Resizes disk to 40GB
• Creates Proxmox VM with:
  • Memory: 16GB RAM
  • CPU: 4 cores (host CPU type)
  • Storage: Uses local-lvm storage
  • Network: Bridged to vmbr0 with DHCP
  • Boot: UEFI with cloud-init support

4. Software Installation #

The cloud-init configuration automatically installs:

• Container Tools: Docker, Docker Compose
• Kubernetes: K3s, kubectl, Helm, K9s
• Development: OpenJDK 17, Maven, Python3, Git
• Infrastructure: Terraform, Ansible
• Monitoring: Chaos Mesh

5. Workshop Content #

• Downloads Splunk Observability Workshop materials
• Sets up Kubernetes secrets with workshop tokens
• Configures private container registry
• Prepares demo applications and content

VM Specifications #

• OS: Ubuntu 24.04 LTS (Noble)
• Memory: 16GB RAM
• CPU: 4 cores
• Disk: 40GB (expandable)
• User: splunk / Splunk123!
• SSH: Password authentication enabled

Environment Variables #

The script configures these environment variables in the VM:

• RUM_TOKEN: Real User Monitoring token
• ACCESS_TOKEN: Data ingest token
• API_TOKEN: Splunk API token
• HEC_TOKEN: HTTP Event Collector token
• HEC_URL: HEC endpoint URL
• REALM: Splunk realm
• INSTANCE: Unique hostname
• CLUSTER_NAME: Kubernetes cluster name

Accessing the VM #

1. Wait for VM creation and boot to complete (5-10 minutes)

2. Find the VM’s IP address in Proxmox console or DHCP logs

3. SSH to the VM:

   bash Copy

   ssh splunk@<vm-ip>
   # Password: Splunk123!

Useful Commands in the VM #

# Check Kubernetes status
kubectl get nodes

# Access Kubernetes dashboard
k9s

# View workshop materials
ls ~/workshop/

# Check environment variables
env | grep -E "(TOKEN|REALM)"

Troubleshooting #

• Invalid SWiPE ID: Verify your workshop registration and ID
• VM creation fails: Check Proxmox storage space and permissions
• Network issues: Ensure vmbr0 bridge is properly configured
• Slow deployment: Allow extra time for cloud-init to complete all installations

Tags #

Created VMs are tagged with: o11y-workshop, noble, k3d