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.

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

Autoscaling support #57

Open
jdheyburn opened this issue Aug 17, 2022 · 0 comments
Open

Autoscaling support #57

jdheyburn opened this issue Aug 17, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@jdheyburn
Copy link

Describe the solution you'd like

  • When using PPS in Strict enforcementMode, when a pod in unschedulable from PPS perspective it will conflict with the Kubernetes cluster-autoscaler (CA)
  • This can cause pods to be stuck in pending state, since CA will not scale up additional nodes
  • CA uses the default-scheduler Filter logic to determine whether the pod can be scheduled on an existing node, not PPSs Filter

Offending logic in cluster autoscaler

Is there any support for autoscaling today, or perhaps in future? If not, is there perhaps a workaround instead?

Anything else you would like to add:
For our use case, we are looking for it to be Strict enforcement mode, since we want some control of how many nodes with a given label are deployed.

Environment: AWS, deployed via kops

  • Kubernetes version: (use kubectl version): v1.21.14
  • Placement Policy Scheduler plugins version: v0.1.0
@jdheyburn jdheyburn added the enhancement New feature or request label Aug 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant