-
Notifications
You must be signed in to change notification settings - Fork 18
feat: enable karpenter ms complex config , make parameter to be configurable #1004
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR enables flexible Karpenter configuration for Microsoft complex scenarios by making VM size optional and allowing the Karpenter nodepool file to be configurable. It adds a new complex nodepool configuration for Azure and includes comprehensive pipeline schedule documentation.
- Adds
karpenter_nodepool_fileparameter to allow custom nodepool configurations - Makes VM_SIZE patching conditional (only when VM_SIZE is provided)
- Introduces a new complex nodepool configuration with multiple VM sizes and a system-surge pool
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
| steps/topology/karpenter/validate-resources.yml | Adds new parameter for configurable nodepool file and makes VM size patching conditional |
| scenarios/perf-eval/nap/kubernetes/karpenter_complex_nodepool.azure.yml | New complex Karpenter nodepool configuration with multiple VM sizes and three nodepools (default, spot, system-surge) |
| PIPELINE_SCHEDULES.md | New documentation file providing comprehensive overview of all pipeline schedules (appears unrelated to main PR purpose) |
e723445 to
2d7d2ac
Compare
make vm size as optional # if not specified, do not patch
make karpenter nodepool file to be configurable/adjustable