Create AKS Automatic and EKS Auto Mode pipeline with AKS Store demo #753
+933
−18
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 30 commits
July 21, 2025 19:39
…ne parameters and update wait conditions
… kubectl commands
…s steps for clarity
…S Terraform inputs
added 16 commits
July 22, 2025 19:23
…urces.yml" This reverts commit 5e395bc.
…gion from the regions array" This reverts commit 7b1d5f3.
…ubectl operations
…rm inputs for EKS automatic mode" This reverts commit 00419f3.
…worker components
…-demo.yml" This reverts commit 6d084ff.
…for clarity" This reverts commit f08af9d.
…orm inputs for EKS automatic mode" This reverts commit 1f79cba.
rafael-mendes-pereira
changed the title
rafael-mendes-pereira
changed the title
added 4 commits
July 22, 2025 22:30
…S Terraform inputs for EKS automatic mode"" This reverts commit 40d385b.
rafael-mendes-pereira
requested review from
alyssa1303,
anson627 and
sumanthreddy29
as code owners
There was a problem hiding this comment.
Pull Request Overview
This PR introduces a new performance evaluation scenario (cluster-automatic) for benchmarking AKS Automatic and EKS Auto Mode clusters using the AKS Store demo application. The implementation includes complete pipeline orchestration, infrastructure configuration, and Kubernetes manifests for deploying a multi-service demo application.
Key changes include:
- New weekly scheduled pipeline for automated benchmarking across Azure (eastus2) and AWS (us-east-2) regions
- Complete AKS Store demo deployment with MongoDB, RabbitMQ, and multiple microservices
- Enhanced AWS Terraform configuration with detailed network architecture and NAT gateway setup
- Reusable pipeline steps for kubectl operations, cluster validation, and demo lifecycle management
Reviewed Changes
Copilot reviewed 11 out of 11 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| cluster-automatic-single-cluster.yml | Weekly scheduled pipeline definition for Azure and AWS benchmarking |
| validate-resources.yml | Azure-specific cluster validation with RBAC setup and kubeconfig conversion |
| execute-aks-store-demo.yml | Simple 60-minute wait step for demo execution |
| collect-aks-store-demo.yml | Demo cleanup orchestration using shared configure-demo template |
| configure-demo.yml | Orchestrates deployment of all three AKS Store manifest components |
| kubectl-manifest.yml | Reusable template for kubectl operations with wait conditions and error handling |
| azure.tfvars | Updates role names from "client" to "automatic" for consistency |
| aws.tfvars | Comprehensive network architecture with private/public subnets and NAT gateways |
| aks-store-virtual-worker.yaml | Virtual worker deployment for load generation (3 replicas, minimal resources) |
| aks-store-virtual-customer.yaml | Virtual customer deployment for load generation (3 replicas, minimal resources) |
| aks-store-all-in-one.yaml | Complete demo application stack with StatefulSets and Services |
Co-authored-by: Copilot <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces a set of changes to support a new performance evaluation scenario (
cluster-automatic) for benchmarking Kubernetes deployments across Azure and AWS clouds. The updates include pipeline configurations, Kubernetes manifests, Terraform inputs, and reusable pipeline steps. Below is a breakdown of the most important changes grouped by theme:Pipeline Configuration Updates:
cluster-automatic-single-cluster.ymlto define weekly benchmarking triggers, variables, and stages for Azure (eastus2) and AWS (us-east-2) regions. This includes job parameters for topology, engine, and timeout settings.new-pipeline-test.ymlto align with thecluster-automaticscenario, replacing placeholders with specific values for cloud, regions, topology, and engine.Kubernetes Manifest Additions:
aks-store-virtual-customer.yamlto define a Kubernetes deployment for the virtual customer component, including environment variables and resource limits.aks-store-virtual-worker.yamlto define a Kubernetes deployment for the virtual worker component with similar configurations.Terraform Input Enhancements:
aws.tfvarswith detailed architecture comments for VPC, subnets, security groups, and EKS configurations. Temporarily disabled NAT gateways and Elastic IPs for testing purposes. [1] [2]azure.tfvarsto rename roles and resources for consistency with thecluster-automaticscenario.Reusable Pipeline Steps:
kubectl-manifest.ymlto standardize Kubernetes manifest application and deletion, with support for waiting on resource readiness.configure-demo.ymlto apply manifests foraks-store-all-in-one,virtual-worker, andvirtual-customerdeployments.collect-aks-store-demo.ymlfor deleting resources post-benchmarking.validate-resources.ymlto refresh credentials, grant RBAC permissions, and apply configurations for thecluster-automatictopology.Execution and Wait Logic:
execute-aks-store-demo.ymlto introduce a wait mechanism for ensuring readiness before proceeding with benchmarking tasks.