Triggering termination for expired node after

From wikieduonline

Revision as of 16:03, 19 January 2023 by Ant (talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Jump to navigation Jump to search

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

Solution: modify ttlSecondsUntilExpired value in provisioner

Karpenter, karpenter.sh, provisioners.karpenter.sh, Karpenter releases, best practices, karpenter.sh/capacity-type, karpenter.sh/discovery, kind: Provisioner, kind: AWSNodeTemplate, kubectl provisioner, TopologyKey, FailedDraining, Evict, DisruptionBlocked, Karpenter logs, controller., ttlSecondsUntilExpired, KEDA, NodePools, Kind: NodePool, Workload Consolidation, Disruption controls

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

Advertising: