Difference between revisions of "Triggering termination for expired node after"
Jump to navigation
Jump to search
(Created page with " controller.node Triggering termination for expired node after 168h0m0s .../... Solution: modify ttlSecondsUntilExpired value in provisioner") |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 3: | Line 3: | ||
Solution: modify [[ttlSecondsUntilExpired]] value in [[provisioner]] | Solution: modify [[ttlSecondsUntilExpired]] value in [[provisioner]] | ||
| + | |||
| + | |||
| + | [[karpenter.sh/do-not-evict: true]] | ||
| + | |||
| + | == See also == | ||
| + | * {{Karpenter}} | ||
| + | |||
| + | [[Category:Karpenter]] | ||
Latest revision as of 16:04, 19 January 2023
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.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
Advertising:
