Cloud Providers

Teabar provisions infrastructure across multiple cloud providers. Each provider offers different tradeoffs in terms of pricing, performance, compliance, and geographic availability.

Supported Providers

Provider Comparison

Pricing

Locations

Provisioning Speed

Kubernetes Options

Compliance & Certifications

Choosing a Provider

Use Hetzner When

• Cost is a priority - Best price-performance for compute
• EU data residency - German and Finnish locations
• Training environments - Maximize participants per dollar
• Self-managed Kubernetes - Talos or K3s clusters

Use AWS When

• Compliance requirements - HIPAA, PCI DSS, FedRAMP
• Global presence needed - 30+ regions worldwide
• AWS service integration - Using RDS, S3, Lambda, etc.
• Managed Kubernetes - EKS with AWS integrations

Use Azure When

• Microsoft ecosystem - Active Directory, Office 365 integration
• Azure service integration - Using Azure SQL, Blob Storage, etc.
• Enterprise agreements - Existing Azure commitments
• Managed Kubernetes - AKS with Azure integrations

Provider Configuration

Organization-Level Setup

Configure provider credentials for your organization:

# Hetzner Cloud
teactl org provider set hetzner 
  --token <HCLOUD_TOKEN>

# AWS
teactl org provider set aws 
  --access-key <AWS_ACCESS_KEY_ID> 
  --secret-key <AWS_SECRET_ACCESS_KEY> 
  --region us-east-1

# Azure
teactl org provider set azure 
  --subscription <AZURE_SUBSCRIPTION_ID> 
  --tenant <AZURE_TENANT_ID> 
  --client-id <AZURE_CLIENT_ID> 
  --client-secret <AZURE_CLIENT_SECRET>

Default Provider

Set a default provider for new environments:

teactl org provider default hetzner

Multiple Providers

You can configure multiple providers and select per-environment:

# blueprint.yaml
spec:
  infrastructure:
    provider: aws  # Override default provider
    region: us-west-2

Multi-Region Environments

Teabar supports environments that span multiple regions within a single provider. This enables:

• Geo-distributed deployments - Resources close to participants worldwide
• Disaster recovery - Cross-region redundancy
• Compliance - Data residency in specific regions

Multi-Region Configuration

spec:
  infrastructure:
    provider: hetzner
    
    # Primary region
    primaryRegion: fsn1
    
    # Additional regions
    regions:
      - location: nbg1
        role: secondary
      - location: hel1
        role: participant-resources
    
    # Cross-region networking
    networking:
      type: wireguard        # wireguard | vpc-peering
      meshEnabled: true      # Full mesh between regions

Regional Resource Placement

Place specific resources in specific regions:

resources:
  clusters:
    - name: control-plane
      region: fsn1           # Primary region
      
    - name: eu-workers
      region: nbg1           # Germany
      
    - name: us-workers
      region: ash            # US East (Ashburn)

  vms:
    - name: participant-{{ .Index }}
      # Auto-place near participants based on their location
      region: auto

Cross-Region Networking

Multi-Region DNS

Teabar automatically configures GeoDNS for multi-region environments:

gitlab.workshop.teabar.dev
├── EU users → fsn1 cluster
├── US users → ash cluster
└── Asia users → nearest available

Blueprint Provider Selection

Specify the provider in your blueprint:

apiVersion: teabar.dev/v1
kind: Blueprint
metadata:
  name: my-workshop
spec:
  infrastructure:
    provider: hetzner
    location: fsn1

  resources:
    - name: participant-vm
      type: vm
      spec:
        size: cx21
        image: ubuntu-22.04

Or allow the environment creator to choose:

spec:
  parameters:
    - name: provider
      type: string
      default: hetzner
      enum: [hetzner, aws, azure]
      description: Cloud provider

  infrastructure:
    provider: "{{ .Parameters.provider }}"

Resource Mapping

Teabar maps abstract resource definitions to provider-specific resources:

VM Sizes

Or specify provider-native sizes directly:

resources:
  - name: participant-vm
    type: vm
    spec:
      size: cx21  # Hetzner-specific
      # or
      size: t3.medium  # AWS-specific

Images

Terraform Backend

Teabar stores Terraform state in PostgreSQL, isolated per environment:

┌─────────────────┐     ┌─────────────────┐     ┌─────────────────┐
│   Environment   │     │   Terraform     │     │   PostgreSQL    │
│   Blueprint     │────►│   Generator     │────►│   State Store   │
└─────────────────┘     └─────────────────┘     └─────────────────┘
                               │
                               ▼
                        ┌─────────────────┐
                        │ Cloud Provider  │
                        │      API        │
                        └─────────────────┘

This ensures:

• State isolation - Each environment’s state is separate
• Locking - Prevents concurrent modifications
• Auditability - Full history of infrastructure changes

Next Steps