Cloud Architecture Examples

Reusable architecture patterns, walkthroughs, and Kubernetes manifests from real-world Azure engagements. Designed to share with partners and customers for reuse across engagements.

Start Here

If you need...	Go to
Quick kubectl commands	aks-fundamentals/
Ingress / networking setup	aks-networking/
Private connectivity between services	aks-private-link/
A reference architecture diagram	ip-cosell/, container-offer/, managed-application/, azure-managed-app-container-offer/

Architecture Patterns

Directory	Description
aks-private-link/	Private Link Service + Private Endpoint — ingress-based and service-based approaches
aks-multi-tenant/	Multi-tenant deployment using namespaces, Helm, and Ingress
aks-monitoring/	Azure Managed Grafana + Prometheus + Loki with Private Endpoints
aks-on-prem-data/	AKS workloads accessing on-premises data sources
cluster-api-capz/	Cluster API for Azure (CAPZ) overview
ip-cosell/	Reference architecture diagram for Azure IP Co-Sell submissions
devops-gitops/	On-premises GitLab → AKS GitOps pipeline architecture

Marketplace Offers

Directory	Description
container-offer/	Architecture for container-based Azure Marketplace offers
managed-application/	Architecture for Azure Managed Applications
azure-managed-app-container-offer/	End-to-end implementation combining Managed Application infrastructure and Container Offer packaging

Kubernetes Examples

Directory	Description
aks-fundamentals/	AKS walkthrough + kubectl one-liners
aks-networking/	Ingress (NGINX, Traefik, ModSecurity), Front Door, advanced networking
aks-services/	Service manifests: ClusterIP, LoadBalancer (public/internal), static IP
aks-storage/	Persistent storage: Azure Files, Managed Disks, BlobFuse
aks-iam-rbac/	Enterprise IAM posture: Entra ID, PIM, persona-based RBAC
aks-apim/	API Management + private AKS + internal Ingress
aks-backup-restore/	Disaster recovery with Velero (Restic and Azure Disk Snapshots)
troubleshooting/	SSH to nodes, debug pods, RBAC utilities

Playground

The playground/ directory is for prototyping architecture diagrams during customer engagements. It is gitignored — nothing in it gets checked in. Once a pattern is generic enough to share, move it to the appropriate top-level directory.

Contributing

See CONTRIBUTING.md for the template and workflow for adding new examples.

lastcoolnameleft/architecture-examples

README