Difference between revisions of "Karpenter controller."

From wikieduonline
Jump to navigation Jump to search
Line 9: Line 9:
 
  [[controller.provisioning]]
 
  [[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] ...
 
  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] ...
 +
 +
[[ERROR controller.provisioning Provisioning failed, launching node, creating cloud provider instance, getting launch template configs, creating launch template, parsing custom user data input unexpected EOF]]
  
 
  DEBUG controller.provisioning [[relaxing soft constraints]]
 
  DEBUG controller.provisioning [[relaxing soft constraints]]

Revision as of 17:52, 4 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] ...
ERROR controller.provisioning Provisioning failed, launching node, creating cloud provider instance, getting launch template configs, creating launch template, parsing custom user data input unexpected EOF
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

Advertising: