How chadmcrowell/k8s-up-and-running works
Project type and purpose
• This is an infrastructure-as-code project (“k8s-up-and-running”) that automates the provisioning of an AKS (Azure Kubernetes Service) cluster and its supporting resources, then deploys a set of microservices onto it.
• Key indicators: multiple IaC tool directories (terraform, bicep, azurecli, powershell), a kubectl/manifests folder with microservice YAMLs, and TLS/Ingress/AppGW scripts.
File structure
• Top-level IaC tool wrappers:
• terraform/ (main.tf, variables.tf, outputs.tf)
• bicep/ (main.bicep)
• azurecli/ (run.sh, scripts)
• powershell/ (template.json, run.ps1)
• Kubernetes deployment manifests under kubectl/manifests for each microservice (cart, catalogue, dispatch, payment, ratings, shipping, user, web) plus supporting infra (mongodb, mysql, rabbitmq, redis).
• appgw/ holds scripts and YAMLs to set up an Azure Application Gateway and ingress.
• tls/ holds cert-manager and ingress TLS configuration.
README
• Confirms that AKS provisioning can be done via Terraform, Bicep, Azure CLI, or PowerShell, then uses kubectl manifests to deploy workloads.
Main components
a. IaC Provisioning Layer
• Four interchangeable toolchains: Terraform, Bicep, Azure CLI scripts, PowerShell scripts.
• Each produces: an Azure Resource Group, AKS cluster, managed identities, networking (VNet, subnets), and optionally an Application Gateway.
b. Azure Platform Layer
• Resource Group containing:
• AKS Cluster (control plane is managed by Azure)
• Azure Application Gateway (appgw) with ingress controllers
• Azure DNS / Public IP / Load Balancer
• TLS Certificates (cert-manager ClusterIssuer in AKS)
c. Kubernetes Cluster Layer
• Namespaces (optional if manifests specify): e.g., default or per-service.
• Deployments + Services for each microservice:
• Frontend “web”
• Business services: cart, catalogue, dispatch, payment, ratings, shipping, user
• Datastores: mongodb, mysql, redis (StatefulSet), rabbitmq
• Ingress resources behind the Application Gateway (tls/new-ingress.yml)
d. External Consumers / CI-CD
• Developers triggering IaC scripts (shell or PowerShell)
• kubectl apply of manifests
• End-users calling the public endpoint via AppGW
Relationships and interactions
• IaC Tools → calls Azure Resource Manager APIs → deploy RG, AKS, networking, AppGW.
• AKS → schedules pods for each Deployment.
• Services expose pods internally.
• Ingress (configured for TLS via cert-manager) routes traffic from AppGW to Services.
• Microservices communicate via internal Service DNS names or via RabbitMQ.
• Datastores present as Services (mongodb, mysql, redis).
Architectural patterns and design principles
• Microservices architecture: each service in its own Deployment + Service.
• Infrastructure as Code: declarative provisioning via multiple tool options.
• GitOps-style: manifests stored in source control.
• Separation of concerns: IaC vs. workload manifests.
• TLS offloading and ingress centralization via AppGW and cert-manager.