Skip to content

Add System Requirements to the README file in the root folder - #43

Merged
paolosalvatori merged 4 commits into
mainfrom
add-system-requirements
Oct 14, 2026
Merged

paolosalvatori merged 4 commits into
mainfrom
add-system-requirements

Conversation

@paolosalvatori

Copy link
Copy Markdown
Collaborator

Motivation

This pull request fixes #36: the README in the main folder doesn't mention hardware requirements yet.

Fixes SMF-946

Changes

Add the following section to the README in the main folder:

System Requirements

Before running the samples, ensure your host machine meets the recommended resource allocations.

Resource Allocations

Resource Minimum Recommended Description
Memory (RAM) 8 GB 16 GB ~3.3 GB for the baseline cluster & LocalStack; additional headroom for workloads
Disk Space 20 GB 30 GB+ ~6 GB for Docker container images and ~7.6 GB for persistent volumes

Baseline Container Footprint

A baseline deployment with 1 system node and 1 user node consumes approximately 3.3 GB of memory across containers:

  • k3d Server (Control Plane): ~1.2 GB
  • System Node: ~0.9 GB
  • LocalStack Azure: ~0.6 GB
  • User Node: ~0.5 GB (allow ~0.5–1.0 GB per additional node)
  • Azurite + k3d Load Balancer: ~0.08 GB

Note

Additional Resource Overhead:
In addition to the base AKS cluster and LocalStack emulator, each specific sample variation can deploy additional Azure resources, services, and Kubernetes workloads. Ensure you account for extra memory and disk capacity based on the specific sample scenario you execute.

Windows / WSL2 Memory Footprint

On WSL2, process memory (vmmemwsl) may appear to expand significantly (e.g., up to 18 GB). This is typically caused by Linux page caching (buff/cache) from unpacking container images rather than active process memory (free -h). Because WSL does not immediately return cached memory to Windows, it can look much heavier than it actually is. To restrict or reclaim WSL memory usage, configure your %USERPROFILE%\.wslconfig:

[wsl2]
memory=12GB
autoMemoryReclaim=dropcache

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The WSL2 example is invalid and leaves its Markdown code fence unclosed.

2 open findings
What changed in this PR

Adds local hardware guidance for running AKS samples with LocalStack.

Changes:

  • Documents RAM, disk, and container usage.
  • Adds WSL2 memory-management guidance.
File Description
README.md Adds system requirements and WSL2 configuration guidance.

🧠 Review effort: Balanced


💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread README.md Outdated
Comment thread README.md Outdated
paolosalvatori and others added 2 commits October 14, 2026 16:34
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Added information about WSL2 memory management and configuration.

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Comment thread README.md Outdated
@paolosalvatori
paolosalvatori merged commit 94c6f98 into main Oct 14, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document hardware requirements for running the samples locally

2 participants