-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: support unknown resources #603
Conversation
counterpart to kubernetes-sigs/karpenter#603
This PR has been inactive for 14 days. StaleBot will close this stale PR after 14 more days of inactivity. |
bump |
Hey @universam1, we've deprecated the configmap as part of the v1beta1 APIs. Due to that, we won't be accepting any changes to the ConfigMap. More details here https://karpenter.sh/docs/upgrading/v1beta1-migration/ As another point, it looks like there are CI failures, and this is a fairly complex problem that warrants a design. Can you come to working group or kubernetes/karpenter-dev to discuss? |
Unknown CLA label state. Rechecking for CLA labels. Send feedback to sig-contributor-experience at kubernetes/community. /check-cla |
|
23e01c0
to
20630f1
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: universam1 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
20630f1
to
40406fb
Compare
Karpenter cannot be used on clusters where custom resources for pods are used, such as device drivers like `/dev/fuse` used with Podman. Following error is logged: ``` karpenter-778b9dbc4f-gk88t {"level":"ERROR",..."logger":"controller.provisioner","message":"Could not schedule pod, incompatible with provisioner \"default\", daemonset overhead={\"cpu\":\"562m\",\"memory\":\"758026799\",\"pods\":\"10\"}, no instance type satisfied resources {\"cpu\":\"1562m\",\"memory\":\"1831768623\",\"pods\":\"11\",\"smarter-devices/fuse\":\"1\"} and requirements karpenter.k8s.aws/instance-category In [c m r], karpenter.k8s.aws/instance-generation Exists >2, karpenter.k8s.aws/instance-hypervisor In [nitro], karpenter.k8s.aws/instance-size NotIn [medium micro nano small], karpenter.sh/capacity-type In [on-demand spot], karpenter.sh/provisioner-name In [default], kubernetes.io/arch In [amd64], kubernetes.io/os In [linux], node.kubernetes.io/node-group In [primary] (no instance type has enough resources)"} ``` Here we add a flag to instruct Karpenter to ignore certain defined resources, which will allow the usage of Karpenter for these clusters.
40406fb
to
a82eb88
Compare
Pull Request Test Coverage Report for Build 8092652375Details
💛 - Coveralls |
Consider looking at #1305! This is our first iteration at solving this problem more comprehensively! |
closing in favor of #1305 |
Description
Karpenter cannot be used on clusters where custom resources for pods are defined, such as device drivers like
/dev/fuse
used with Podman and many more (see references).Following error is logged:
Here we add a flag to instruct Karpenter to ignore certain defined resources, which will allow the usage of Karpenter for these clusters.
Fixes #751
Fixes aws/karpenter-provider-aws#2390
Fixes aws/karpenter-provider-aws#2899
Fixes navvis-dev/karpenter#3
Fixes aws/karpenter-provider-aws#3535
Fixes https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/3717
Fixes #308
Fixes aws/karpenter-provider-aws#3315
Fixes aws/karpenter-provider-aws#3693
How was this change tested?
This fork is run in dozen of production clusters.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.