Skip to content

docs: Revise guidance for enabling Azure/AKS features in Karpenter - #1876

Open
Wilson (wdarko1) wants to merge 3 commits into
Azure:mainfrom
wdarko1:docs/feature-enablement-guide
Open

docs: Revise guidance for enabling Azure/AKS features in Karpenter#1876
Wilson (wdarko1) wants to merge 3 commits into
Azure:mainfrom
wdarko1:docs/feature-enablement-guide

Conversation

@wdarko1

Copy link
Copy Markdown
Contributor

Created guidance document for enabling Azure/AKS features in Karpenter by refining language and clarifying points. Adjusted checklist items for better readability and understanding.

Description
A feature enabled guide for contributors. This includes gotchas and builds on previous maintainer/reviewer comments to improve contribution quality.

Updated the guidance document for enabling Azure/AKS features in Karpenter by refining language and clarifying points. Adjusted checklist items for better readability and understanding.
Copilot AI lite review requested due to automatic review settings August 27, 2026 19:55

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.

Pull request overview

Adds a new design-guidance document intended to help contributors consistently expose new Azure/AKS features in the Karpenter Azure provider (covering API surfacing decisions, defaulting, hashing/drift, validation, filtering, provisioning paths, and testing expectations).

Changes:

  • Introduces a comprehensive “feature enablement” checklist and decision framework derived from past feature landings.
  • Documents common failure modes (defaults, hash bumps, CEL rules, cache keys, VM vs AKS Machine API parity, bootstrapping drift) and where to implement changes.
  • Provides a testing/production-readiness rubric to align contributor PRs with reviewer expectations.

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

Comment thread designs/0000-feature-enablement-guide.md Outdated
Comment thread designs/0000-feature-enablement-guide.md Outdated
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings August 27, 2026 20:08

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.

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Suppressed comments (1)

Previously missed (1) — in code that hasn't changed since the last review.

designs/0000-feature-enablement-guide.md:309

  • Severity: Low; Category: Correctness — This guidance points contributors to inplaceupdate/utils.go, but that path doesn’t exist in the repo. The in-place update field structs live under pkg/controllers/nodeclaim/inplaceupdate/utils.go, so following this as written will send people to the wrong location (or make them think the code is missing).
* Add it to `vmInPlaceUpdateFields` and/or `aksMachineInPlaceUpdateFields`
  (`inplaceupdate/utils.go`). They are **not symmetric** — VM identities are handled
  server-side for AKS machines and are deliberately absent from the machine struct.

Clarified default behavior for Karpenter features to align with AKS AgentPool API.
Copilot AI review requested due to automatic review settings August 27, 2026 20:13

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.

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

Comment on lines +121 to +122
The default behavior for any added feature in Karpenter should, where possible, match the defaults in the AKS Agentpool API.
Also for Azure features, the Karpenter path should expose similar control to the AKS Agentpool API.
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.

2 participants