Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Question: how Karpenter play with the default PodTopologySpread part of KubeSchedulerConfiguration? #1197

Closed
myaser opened this issue Apr 22, 2024 · 3 comments
Closed

Question: how Karpenter play with the default PodTopologySpread part of KubeSchedulerConfiguration? #1197

myaser opened this issue Apr 22, 2024 · 3 comments
Labels
lifecycle/closed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@myaser
Copy link

myaser commented Apr 22, 2024 •
edited
Loading

I was wondering what karpenter would do by default in terms of spreading pods across nodes and availability zones?

  • is there any default built in karpenter in case a pod did not define topologySpreadConstraints?
  • does it honor the built in constraints of the scheduler?
  • in case the default was customized, would karpenter know and honor the new default?

related:
CA related issue
@github-actions GitHub Actions
Copy link

github-actions bot commented May 7, 2024

This issue has been inactive for 14 days. StaleBot will close this stale issue after 14 more days of inactivity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 7, 2024
@myaser
Copy link
Author

myaser commented May 8, 2024

please remove the stale state

@github-actions github-actions bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 8, 2024
@github-actions GitHub Actions
Copy link

This issue has been inactive for 14 days. StaleBot will close this stale issue after 14 more days of inactivity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 22, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/closed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@myaser