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

# of Pods for Bottlerocket Nodes is calculated incorrectly #1677

Closed
tzneal opened this issue Apr 15, 2022 · 5 comments
Closed

# of Pods for Bottlerocket Nodes is calculated incorrectly #1677

tzneal opened this issue Apr 15, 2022 · 5 comments
Assignees
@tzneal
Labels
bug Something isn't working

Comments

@tzneal
Copy link
Contributor

tzneal commented Apr 15, 2022

Version

Karpenter: v0.8.2

Expected Behavior

The number of pods is computed correctly for Bottlerocket nodes.

Actual Behavior

What we think the node will have:

Allocatable:
  cpu:                192
  ephemeral-storage:  100Pi
  memory:             363724Mi
  pods:               737

What it actually has:

Bottle Rocket
Allocatable:
  attachable-volumes-aws-ebs:  39
  cpu:                         191450m
  ephemeral-storage:           17933882132
  hugepages-1Gi:               0
  hugepages-2Mi:               0
  memory:                      387778060Ki
  pods:                        110

AL2
Allocatable:
  attachable-volumes-aws-ebs:  39
  cpu:                         191450m
  ephemeral-storage:           18242267924
  hugepages-1Gi:               0
  hugepages-2Mi:               0
  memory:                      379235016Ki
  pods:                        737

Steps to Reproduce the Problem

Set the AMI Family to Bottlerocket, deploy something that causes a large node to be created and inspect the # of pods on the node object we create vs what it's set to when kubelet has started.
@tzneal tzneal added the bug Something isn't working label Apr 15, 2022
@tzneal
Copy link
Contributor Author

tzneal commented Apr 15, 2022

Related: bottlerocket-os/bottlerocket#1721

@github-actions
Copy link
Contributor

github-actions bot commented May 6, 2022

Labeled for closure due to inactivity in 10 days.

@github-actions
Copy link
Contributor

Labeled for closure due to inactivity in 10 days.

@billrayburn billrayburn assigned billrayburn and tzneal and unassigned tzneal and billrayburn May 27, 2022
@github-actions
Copy link
Contributor

Labeled for closure due to inactivity in 10 days.

@tzneal tzneal reopened this Jun 28, 2022
@tzneal
Copy link
Contributor Author

tzneal commented Jun 29, 2022

Talked to @suket22 , this was most likely caused by me testing with a new instance type.

@tzneal tzneal closed this as completed Jun 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tzneal tzneal

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tzneal @billrayburn