What consequences can arise from not setting resource limits in Kubernetes?

If resource limits (CPU, memory) are not configured for containers in Kubernetes, the following issues may arise:

• Resource overuse: Containers may consume more resources than expected, leading to node resource exhaustion.
• Node crashes: Due to lack of memory or CPU, nodes may become unstable or reboot.
• Application instability: Other pods on the same node may experience resource shortages, degrading their performance.
• Lack of control: Without limits, it is difficult to predict cluster behavior and plan scaling.

Therefore, it is recommended to always set requests (minimum guarantees) and limits (maximum values) for container resources to ensure cluster stability and predictability.