aws-samples / aws-samples/appmod-blueprints

Create dedicated EKS Auto Mode nodepools for addons

Open
#596 1 comment 0 reactions 0 assignees View on GitHub
agentic-platform enhancement
Dominant language
Shell
Stars
105
Forks
62
Avg merge
11h 17m
Merged PRs (30d)
76

Description

**Parent:** #584
**Priority:** Medium

EKS Auto Mode uses a default nodepool for all workloads. Create dedicated nodepools for platform addons to:
- Isolate platform workloads from application workloads
- Set resource limits and instance types per addon category
- Support GPU nodepools for ML/AI addons
- Allow cost attribution per nodepool

Implementation:
- Add nodepool definitions to the PlatformCluster composition or as separate Crossplane resources
- Configure addon charts to use `nodeSelector` or `nodeAffinity` targeting the dedicated nodepool
- Parameterize nodepool name via `global.clusterName` (e.g., `system-{clusterName}`)

Contributor guide

Open the contributing guide

Research direction

Start with the PlatformCluster composition or the separate Crossplane resources, then inspect the addon charts and their global.clusterName values. Done means dedicated nodepools cover the platform addon categories, addon scheduling targets them, and the configuration supports resource and instance settings, GPU workloads, and cost attribution.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, helm, kubernetes
Domain
cloud, devops, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.