Evict any already-running pods that do not tolerate the taint.
Currently enforced by NodeController.
NoSchedule
Do not allow new pods to schedule onto the node unless they tolerate the
taint, but allow all pods submitted to Kubelet without going through the
scheduler to start, and allow all already-running pods to continue
running. Enforced by the scheduler.
PreferNoSchedule
Like TaintEffectNoSchedule, but the scheduler tries not to schedule
new pods onto the node, rather than prohibiting new pods from scheduling
onto the node entirely. Enforced by the scheduler.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-04 UTC."],[[["This document provides reference documentation for the `NodeTaint.Types.Effect` enum within the Google Cloud GKE Multi-Cloud v1 API."],["The `NodeTaint.Types.Effect` enum represents the taint effect applied to a node, with version 2.8.0 being the latest and version 1.0.0-beta01 as the earliest documented."],["The enum defines four possible effects: `NoExecute`, which evicts pods; `NoSchedule`, which prevents new pods from being scheduled; `PreferNoSchedule`, which prefers not to schedule new pods; and `Unspecified`, indicating no effect is set."],["Each effect is described in terms of how it influences pod scheduling and execution on the node, specifically noting whether it's enforced by the NodeController or the scheduler."]]],[]]