Kubernetes
Hard
Concepts
A node gets a NoExecute taint. A pod already running on it tolerates the taint with tolerationSeconds: 300. What happens?
Select your answer:
Show answer and explanation
Answer: It keeps running for 300 seconds, then is evicted
Explanation
NoExecute evicts running pods that don't tolerate the taint. A pod that tolerates it without tolerationSeconds stays forever. With tolerationSeconds, the pod stays bound for that many seconds after the taint is added and is then evicted. Kubernetes gives pods this kind of toleration for the node.kubernetes.io/not-ready and unreachable taints, with a default of 300 seconds.
More hard Kubernetes questions
- What does a DNS lookup of a headless Service (clusterIP: None) with a selector return?
- What does externalTrafficPolicy: Local do on a NodePort or LoadBalancer Service?
- In a NetworkPolicy ingress rule, what is the difference between putting namespaceSelector and podSelector in the same 'from' entry and putting them in two separate entries?
- Two controllers read the same Deployment and both send an update based on what they read. How does the API server stop the second update from silently overwriting the first?
- A namespace has been stuck in Terminating for hours. What is the most likely cause?
- What does podManagementPolicy: Parallel change in a StatefulSet?