Skip to content

Environments

Environment Purpose Helm values Terraform K8s namespace Deployed by
local A single developer's own machine (Docker Desktop k3d/K3s) helm/akshayabazaar/values-local-staging.yaml none - no cloud infra staging (inside the local k3d cluster) you, manually, via scripts/deploy-local.ps1
dev Shared, low-stakes tier for ad-hoc builds helm/akshayabazaar/values-dev.yaml terraform/environments/dev/ (scaffolded, never applied) akshayabazaar-dev Jenkins, automatically, on every master push
staging Pre-production smoke-test tier; every release build lands here first helm/akshayabazaar/values-staging.yaml terraform/environments/staging/ akshayabazaar-staging Jenkins, automatically, on every release-tag build
production ("prod") Production helm/akshayabazaar/values-production.yaml terraform/environments/production/ akshayabazaar-production Jenkins, with a manual approval gate

Why "prod" means "production" here

This repository has used values-production.yaml / terraform/environments/production/ / akshayabazaar-production consistently since the infrastructure was first built. There is no separate prod naming anywhere in the codebase - this portal's "Production" section documents that existing name rather than introducing a second one for the same environment.

local vs. dev - not the same thing

  • local is k3d running inside Docker Desktop on your own machine. Nothing in Terraform provisions it; its staging Kubernetes namespace name is a k3d-cluster-internal detail, entirely unrelated to the real akshayabazaar-staging namespace on the shared K3s node.
  • dev is a real (if minimal) tier on real Hetzner/Cloudflare infrastructure, reachable by anyone with network access, for testing that needs more than one machine's view.

Production is structural-only in this portal's guidance

Every command in this portal that could reach production is clearly labeled, and none are executed as part of building or maintaining this documentation. See Deployment → Production for the full separation from staging.