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

Karpenter is recreating the same type of node over a period of time and deleting it in parallel #1851

Open
bparamjeet opened this issue Nov 29, 2024 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@bparamjeet
Copy link

Description

Observed Behavior:
Karpenter is recreating the same type of node over a period of time and deleting it in parallel when replicas are increased.

Expected Behavior:
Karpenter should not consolidate often when replicas are increased and new nodes are created , deleted over a period of time marking the pods to be shifted to new nodes.

Reproduction Steps (Please include YAML):

  • Create multiple nodepools with same weights and each for an AZ.
  • Create a deployment with 1 replica without any nodeselectors.
  • Increase the replica count to 10
  • Karpenter will create multiple nodeclaims and the pods will be re-shuffled over period of time.

Versions:

  • Karpenter Version: 1.0.5
  • Kubernetes Version (kubectl version): v1.31
Screenshot 2024-11-29 at 4 41 36 PM Screenshot 2024-11-29 at 6 05 02 PM Screenshot 2024-11-29 at 6 05 07 PM
@bparamjeet bparamjeet added the kind/bug Categorizes issue or PR as related to a bug. label Nov 29, 2024
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Nov 29, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If Karpenter contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

2 participants