Update NodePool.Status with node drift information. #6166
Labels
feature
New feature or request
metrics-audit
Issues that should be captured as part of the upcoming v1beta1 Karpenter metrics audit
Description
What problem are you trying to solve?
Currently, there is no clear way to identify how many nodes have drifted from the current hash (nodepool hash and ec2nodeclass hash). To determine the node rotation progress, we will have to look into individual node objects, nodeclaims, nodepool and nodeclass.
Since Karpenter controller identifies and rotates the drifted nodes, I am assuming the controller already maintains the list of drifted nodes (if not, identifies the drifted nodes in every reconciliation.) It will be helpful to surface this information in the NodePool status.
for ex:
How important is this feature to you?
This feature will be very useful to identify the progress of node rotation whenever we change AMIs or trigger any other form of upgrades by updating the nodepool or ec2nodeclass.
The text was updated successfully, but these errors were encountered: