You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the feature
I would like to request extending ASG launch lifecycle support with following usecase: when node is being launched, currently NTH only takes into account Node's Ready condition to determine if node is truly ready. I would like NTH to also take int oconsideration lack of some taints. Karpenter has such feature here called startupTaints.
Basically it would mean adding new config option allowing specifying list of taints that needs to be absent in order to consider node as Ready in NTH sense. Then, here, function isNodeReady needs to check also, based on said config option, if there is any taint on the node that should not be there.
Is the feature request related to a problem?
If the CNI is not being fully ready, Node might be considered by NTH as Ready despite the fact it cannot run any workloads.
Describe alternatives you've considered
Migrating to Karpneter but it is currently time consuming.
The text was updated successfully, but these errors were encountered:
Describe the feature
I would like to request extending ASG launch lifecycle support with following usecase: when node is being launched, currently NTH only takes into account Node's
Ready
condition to determine if node is truly ready. I would like NTH to also take int oconsideration lack of some taints. Karpenter has such feature here calledstartupTaints
.Basically it would mean adding new config option allowing specifying list of taints that needs to be absent in order to consider node as
Ready
in NTH sense. Then, here, functionisNodeReady
needs to check also, based on said config option, if there is any taint on the node that should not be there.Is the feature request related to a problem?
If the CNI is not being fully ready, Node might be considered by NTH as
Ready
despite the fact it cannot run any workloads.Describe alternatives you've considered
Migrating to Karpneter but it is currently time consuming.
The text was updated successfully, but these errors were encountered: