Include Karpenter-provisioned nodes into consideration #7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses #3 : Karpenter Support
Karpenter does not provision nodes as part of a node group/pool. However, they are still useful to see when listing groups or pools of nodes. This development allows for nodes that have been provisioned by karpenter to be identified by the plugin.
Note that multiple instance types can be present for a single karpenter provisioner, so output can look like this:
# list ❯ kubectl nodepools list NAME NODES TYPE (Karpenter) default 2 c6a.2xlarge, m5.2xlarge main-m52xl-2 4 m5.2xlarge
This has been achieved by restructuring how the
nodepool
struct is implemented, by having "Types" be a set rather than a single value.