assign_to_non_existent_node

Problem Set
Cloud Management System Failure

Description

The problem runs on social-network. Simulate a fault where pods are assigned to non-existent nodes in the Kubernetes cluster. The deployment `user-service` is configured with a nodeSelector pointing to a non-existent node (extra-node), causing pods to remain in Pending state. Inject the fault by configuring pod scheduling to assign pods to nodes that do not exist.

Tags

Cloud Management System Failure, social-network