Ignore Node Readiness Controller Taints

[njtran]

Description

What problem are you trying to solve?
Node Readiness Controller is beta in 1.36. it auto-adds taints with a readiness.k8s.io prefix based on CRD Rules in the cluster. The taint logic in statenode.go should probably ignore these taints

How important is this feature to you?
Not sure how widespread this will be with Karpenter users, not sure what adoption is.

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[samuel-esp]

I've pointed a similar concern in #2925. The release of NodeReadinessController might require changes to the Karpenter startupTaints paradigm

[jmdeal]

/accepted

[jmdeal]

/triage accepted
/priority important-soon

The release of NodeReadinessController might require changes to the Karpenter startupTaints paradigm

I think there are two concerns - the management of the startup taints and how Karpenter responds to the precense of taints on nodes. Currently Karpenter doesn't actually enforce the application of startup taints, that's up to the cloudprovider implementation. The important aspect of startup taints for upstream Karpenter is that Karpenter shouldn't consider the NodeClaim as initialized until the startup taints have been removed. I think the logic for this controller should be relatively straightforward since all taints must have the same prefix.