Triggering termination for expired node after

From wikieduonline

Jump to navigation Jump to search

controller.node Triggering termination for expired node after 168h0m0s .../...

Solution: modify ttlSecondsUntilExpired value in provisioner

karpenter.sh/do-not-evict: true

See also[edit]

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

Retrieved from "https://www.wikieduonline.com/index.php?title=Triggering_termination_for_expired_node_after&oldid=219454"

Karpenter

Advertising: