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

feat: add possibility to use Karpenter #245

Closed
mglotov opened this issue Jan 31, 2022 · 0 comments · Fixed by #349
Closed

feat: add possibility to use Karpenter #245

mglotov opened this issue Jan 31, 2022 · 0 comments · Fixed by #349
Assignees

Comments

@mglotov
Copy link
Contributor

mglotov commented Jan 31, 2022

Karpenter is an open-source node provisioning project built for Kubernetes. Karpenter improves the efficiency and cost of running workloads on Kubernetes clusters by:

  • Watching for pods that the Kubernetes scheduler has marked as unschedulable
  • Evaluating scheduling constraints (resource requests, nodeselectors, affinities, tolerations, and topology spread constraints) requested by the pods
  • Provisioning nodes that meet the requirements of the pods
  • Removing the nodes when the nodes are no longer needed

Expected Behavior

Fully migrate from Cluster Autoscaler to Karpenter or provide a possibility to

  • switch between solutions
  • enable/disable them

Current Behavior

Only cluster-autoscaler is used to scale node pools automatically.

@mglotov mglotov changed the title feat: Karpenter feat: add possibility to use Karpenter Jan 31, 2022
@khalezin khalezin self-assigned this Mar 21, 2023
khalezin added a commit that referenced this issue Mar 21, 2023
khalezin added a commit that referenced this issue Mar 23, 2023
khalezin added a commit that referenced this issue Mar 23, 2023
@khalezin khalezin mentioned this issue Mar 23, 2023
7 tasks
khalezin added a commit that referenced this issue Mar 23, 2023
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 a pull request may close this issue.

2 participants