Comments (9)
i'm using the same label and the taints in the deployment manifests, but i still see the below error in karpenter logs
{"level":"ERROR","time":"2024-05-29T16:01:08.723Z","logger":"controller.provisioner","message":"Could not schedule pod, incompatible with nodepool "default", daemonset overhead={"cpu":"736m","memory":"1067557632","pods":"8"}, incompatible requirements, label "application" does not have known values","commit":"6b868db","pod":"default/rancher-test-98559869c-5vdw8"}
{"level":"ERROR"
Warning FailedScheduling 0s karpenter Failed to schedule pod, incompatible with nodepool "default", daemonset overhead={"cpu":"766m","memory":"1193386752","pods":"9"}, incompatible requirements, label "application" does not have known values
from karpenter.
failing to understand why is the karpenter failing to spin up a node when the labels and nodeselctors match and using the same tolerations in deployment file
from karpenter.
The log you provided has a commit indicating that it's from Karpenter v0.36.0 and has a different NodePool name than the Provisioner you provided. Also a Provisioner wouldn't be compatible with v0.36.0, dual support for the alpha and beta APIs was dropped at v0.33.0. Do you have a NodePool in your cluster that you would expect this pod to schedule to other than "default", which Karpenter considers incompatible?
from karpenter.
sorry, i didnt get you completely since i'm new to karpenter, i just have a single nodepool which is the default one
kubectl get nodepool
NAME NODECLASS
default default
from karpenter.
is there any difference between nodepool and provisioners? my understanding may be incorrect, i deployed karpenter as an addon, and using helm i will have to deploy multiple provisioners,
from karpenter.
{{- range .Values.provisioners }}
apiVersion: karpenter.sh/v1alpha5
kind: Provisioner
metadata:
name: {{ .name }}
spec:
labels:
{{- range $key, $value := .labels }}
{{ $key }}: {{ $value | quote }}
{{- end }}
requirements:
- key: "node.kubernetes.io/instance-type"
operator: In
values:
{{- range .instanceTypes }}
- {{ . }}
{{- end }}
- key: "karpenter.sh/capacity-type"
operator: In
values:
{{- range .capacityType }}
- {{ . }}
{{- end }}
limits:
resources:
cpu: {{ .limit }}
{{- if .taints }}
taints:
- effect: NoSchedule
key: {{ .taints.key | quote }}
value: {{ .taints.value | quote }}
{{- end }}
providerRef:
name: {{ .providerReference }}
ttlSecondsAfterEmpty: 30
{{- end }}
this is the provisioner templabe file i'm using
from karpenter.
i would like to have the pods scheduled on the nodes which are having the same config i pass through the provisioners and not the default nodepool
from karpenter.
@jmdeal , correct me if my understanding is wrong, for karpenter 0.36.x, we have karpenter node pools instead of karpenter provisioners? from the github repo i see nodepool repo instead of a provisioner repohttps://github.com/aws/karpenter-provider-aws/tree/v0.36.1/charts/karpenter/crds
from karpenter.
Provisioners replaced NodePools in Karpenter v0.32.0, and support for Provisioners was completely removed in v0.33.0. You'll need to replace your provisioners with equivalent nodepools for them to work with v0.36.x. You can find more information in the v1beta1 migration guide.
from karpenter.
Related Issues (20)
- Karpenter provisions too large machine HOT 8
- Continuation of issue#: 6024 HOT 1
- Changes in `AMISelectorTerms` doesn't result in drift HOT 2
- Run Karpenter on Fargate HOT 3
- How to add EFA to instances (or custom resources requests) HOT 5
- ERROR: Karpenter not authorized to perform: iam:PassRole HOT 12
- Health Probe Timeout and Node Claiming Issues Following Upgrade to Karpenter v0.36.1 HOT 5
- karpenter.k8s.aws/instance-size will not work with `xlarge` HOT 3
- v1beta1 Migration a node tag need to be added to provisioner nodes to allow termination HOT 4
- Nodes are created but are not being registered to the cluster HOT 6
- Persistent Issue with Karpenter v0.36.0: Node Creation and Scheduling Failure Despite Resource Adjustments HOT 2
- Karpenter 0.16.3 helm chart unable to consolidate cluster HOT 5
- Allow the AMI Selector Terms to select based off of release_version HOT 1
- add "maintenance windows" for expiring nodes HOT 2
- Karpenter nodes are not coming up HOT 1
- When spot is not available, karpenter fails to create an on-demand (within the 45 seconds documented time) HOT 4
- Karpenter always change all node at 11:50 PM (UTC) HOT 1
- Validation errors occur due to CRD changes in the Karpenter 0.37 upgrade HOT 3
- ta3.small instance type seems to be missing HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from karpenter.