Skip to content

docs: add pool-level feature guide for Machine API wiring#1520

Draft
comtalyst wants to merge 1 commit intomainfrom
docs/pool-level-feature-guide
Draft

docs: add pool-level feature guide for Machine API wiring#1520
comtalyst wants to merge 1 commit intomainfrom
docs/pool-level-feature-guide

Conversation

@comtalyst
Copy link
Copy Markdown
Collaborator

@comtalyst comtalyst commented Mar 16, 2026

Description

Adds a developer guide (designs/0009-pool-level-feature-guide.md) that codifies the repeating pattern of adding AKS pool-level features to Karpenter.

Many features follow the same passthrough pattern (CRD field → Machine API parameter) but each requires significant ramp-up time to locate the right files and understand the conventions. This guide provides:

  • Step-by-step checklist with exact file paths for each phase
  • Template code snippets for configure*() helpers, unit tests, and CRD fields
  • Complexity spectrum with real examples (EncryptionAtHost → LinuxOSConfig)
  • Catalog of ~12 currently unwired Machine API fields awaiting future work
  • Notes on drift detection, instance type filtering, and bootstrapping client path

How was this change tested?
Documentation only — no code changes.

Release Note

NONE

Codifies the repeating pattern of adding AKS pool-level features to
Karpenter: CRD field → Machine API parameter passthrough. Includes
step-by-step checklist, template code snippets, complexity spectrum
with real examples, and catalog of currently unwired Machine API fields.

Addresses the observation that each pool-level feature follows the
same pattern but requires significant ramp-up time to locate the
right files and understand the conventions.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@comtalyst comtalyst marked this pull request as draft March 17, 2026 00:37
@comtalyst comtalyst marked this pull request as ready for review March 17, 2026 00:59
@comtalyst comtalyst marked this pull request as draft March 17, 2026 01:05
@comtalyst comtalyst added the experimental-please-ignore Issues or PRs that should be ignored unless been told otherwise. label Apr 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

experimental-please-ignore Issues or PRs that should be ignored unless been told otherwise.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant