ExtendedResourceToleration not supported

[universam1]

Description

Observed Behavior:

When using Admission controller: ExtendedResourceToleration functionality it causes Karpenter to fail to schedule nodes. It is defined via a resource request which will trigger the Admission controller to create a Toleration for the matching taint.

However, Karpenter presumptuously believes it should decide to fail as it "cannot provide that resources".

resources:
  requests:
    robovision.ai/monkeys: 3

Expected Behavior:

Karpenter to ignore unknown resources, the same way as ClusterAutoscaler does!

Reproduction Steps (Please include YAML):

Follow the steps in https://medium.com/robovision-ai/use-kubernetes-extendedresourcetoleration-to-keep-out-non-gpu-pods-c180f5c5e76d

• 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

[k8s-ci-robot]

This issue is currently awaiting triage.

If Karpenter contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.