Skip to content

Conversation

@tallaxes
Copy link
Collaborator

Description

Update sigs.k8s.io/karpenter to v1.8.2, enable static capacity support

How was this change tested?

  • make presubmit
  • FOCUS=StaticCapacity make az-upstream-e2etests

Does this change impact docs?

  • Yes, PR includes docs updates
  • Yes, issue opened: #
  • No

Release Note


@tallaxes tallaxes added the area/dependency Issues or PRs related to dependency changes label Jan 21, 2026
@tallaxes tallaxes self-assigned this Jan 21, 2026
@tallaxes
Copy link
Collaborator Author

Manual run of upstream StaticCapacity passed 10/12, the failures are likely due to metric-server etc. sticky overprovisioning, but have not investigated yet

$ FOCUS=StaticCapacity make az-upstream-e2etests
...
Summarizing 2 Failures:
  [FAIL] StaticCapacity Dynamic NodeClaim Interaction [It] should provision dynamic nodeclaims when static nodeclaims cant satisfy pod constraints
  /go/pkg/mod/sigs.k8s.io/[email protected]/test/suites/regression/staticcapacity_test.go:423
  [FAIL] StaticCapacity Edge Cases [It] should handle NodePool deletion gracefully
  /go/pkg/mod/sigs.k8s.io/[email protected]/test/suites/regression/staticcapacity_test.go:507

Ran 12 of 74 Specs in 3486.442 seconds
FAIL! -- 10 Passed | 2 Failed | 0 Pending | 62 Skipped

@tallaxes tallaxes added area/core Issues related with karpenter-core/upstream and removed area/dependency Issues or PRs related to dependency changes labels Jan 21, 2026
@hakman hakman mentioned this pull request Jan 21, 2026
3 tasks
Base automatically changed from tallaxes/go1.25 to main January 22, 2026 22:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/core Issues related with karpenter-core/upstream

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants