feat: Added additional topology spread constraint #3190
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
While a production cluster should definitely be multi-zonal, some dev/test clusters may only be in a single zone. Regardless, we don't want the multiple karpenter pods on a single host.
Added additional topology spread constraint
✅ Deploy Preview for karpenter-docs-prod canceled.
|
ellistarn
reviewed
Jan 10, 2023
|
@wpbeckwith Ping for the requested changes. Otherwise, PR looks good! |
|
@runningman84 This PR has gone stale. If you want to open a PR that adds preferred hostname anti-affinity, we would be happy to accept it. |
|
Sorry been busy with a cloud migration. We'll get this submitted this weekend. |
sftim
reviewed
Feb 28, 2023
jonathan-innis
approved these changes
Feb 28, 2023
runningman84
approved these changes
Mar 1, 2023
johngmyers
pushed a commit
to johngmyers/karpenter
that referenced
this pull request
May 31, 2024
Merge in DEL/karpenter-fork from DELIVERY-8215_update_to_0.27.0 to main * commit 'c5b7235218996a4579180ab4811afe82c884ee9f': chore: Bump `karpenter-core` to latest (aws#3548) BREAKING CHANGE: Convert preferred anti-affinity to required anti-affinity (aws#3543) test: Fix daemonset preemption in testing to be `PreemptLowerPriority` (aws#3544) chore: Move instance to providers (aws#3509) docs: cleanup `aws.tags` and `specs.tags` docs (aws#3540) docs: Add Canva to Adopters (aws#3541) fix: fixed an issue where only using owners in amiSelector resulted in a failure (aws#3533) feat: add featureGates.driftEnabled to helm chart values (aws#3521) chore: Release v0.26.1 (aws#3519) fix: inflight IP tracking when CreateFleet returns an error (aws#3515) chore: add more integration test logs (aws#3511) chore(deps): bump github.com/aws/aws-sdk-go from 1.44.195 to 1.44.212 in /test (aws#3508) test: if the test fails, identify the names of the created nodes (aws#3504) chore: Move instancetypes to providers (aws#3478) feat: Added additional topology spread constraint (aws#3190) chore: Release v0.26.0 (aws#3506) test: fix test panic (aws#3503) chore: fix pco allocation strategy for ec2 fleet (aws#3502) docs: Add Docker to adopters list (aws#3500) Typo (aws#3487)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #
Description
While a production cluster should definitely be multi-zonal, some dev/test clusters may only be in a single zone. Regardless, we don't want the multiple karpenter pods on a single host if possible.
How was this change tested?
Deployed to multiple clusters with one or multiple zones and verified karpenter pods are on different hosts
Does this change impact docs?
Release Note
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.