Why should you care?

CloudVerse multi-cloud landing zones share modules for VPC, IAM, and logging.

See it live — copy this example

Use AWS/Azure/GCP free tier or local Docker/Kind. Sketches and YAML are meant to be typed and adapted.

# modules/aks/main.tf (CloudVerse)
variable "cluster_name" { type = string }
resource "azurerm_kubernetes_cluster" "cv" {
  name                = var.cluster_name
  location            = var.location
  resource_group_name = var.rg_name
  dns_prefix          = var.cluster_name
  default_node_pool {
    name       = "system"
    node_count = 3
    vm_size    = "Standard_D4s_v5"
  }
  identity { type = "SystemAssigned" }
}

What happened?

• Modules encapsulate patterns.
• State backends and workspace/env separation prevent cross-environment accidents.

Practice next

1. Init backend (azurerm or s3).
2. Write a module.
3. terraform plan -var-file=dev.tfvars.
4. Add output for kubeconfig host.
5. Use terraform fmt in CI.

Remember

HCL modules. Plan before apply. Remote state + locking.

CloudVerse AKS module

Three product lines need identical cluster baselines.

Outcome: One module; different tfvars per line.