Difference between revisions of "Karpenter controller."
Jump to navigation
Jump to search
| Line 29: | Line 29: | ||
[[controller.node]] Triggering termination after 5m0s for empty node .../... | [[controller.node]] Triggering termination after 5m0s for empty node .../... | ||
| − | [[controller.node]] Discovered 495 [[EC2 | + | [[controller.node]] Discovered 495 [[EC2 instance types]] |
== Related == | == Related == | ||
Revision as of 16:14, 3 January 2023
controller.provisioning controller.provisioning.cloudprovider controller.termination controller.node controller.aws.launchtemplate controller.aws.pricing
controller.provisioning ERROR controller.provisioning Could not schedule pod, incompatible with provisioner "XXXXXX" incompatible requirements, key karpenter.sh/provisioner-name In [XXXXXX] not in karpenter.sh/provisioner-name In [XXXXXXX] ...
DEBUG controller.provisioning relaxing soft constraints
controller.termination Cordoned node ... controller.termination Deleted node ...
controller.aws.launchtemplate controller.aws.launchtemplate Deleted launch template ...
controller.provisioning.cloudprovider controller.provisioning.cloudprovider Created launch template ...
controller.node
controller.node Triggering termination for expired node after 168h0m0s .../...
Solution: modify ttlSecondsUntilExpired value in provisioner
controller.node Triggering termination after 5m0s for empty node .../...
controller.node Discovered 495 EC2 instance types
Related
See also
- Karpenter, Karpenter releases, best practices,
karpenter.sh/capacity-type, karpenter.sh/discovery,kind: Provisioner, kind: AWSNodeTemplate,kubectl provisioner, TopologyKey, FailedDraining, Evict, Karpenter logs,controller., ttlSecondsUntilExpired, KEDA - Kubernetes controllers: Ingress,
controller., AWS Load Balancer controller, kubectl describe ingressclass nginx
Advertising:
