Description
The problem runs on social-network. Simulate a fault where persistent volume affinity constraints are violated. The deployment `user-service` is configured with a PersistentVolume (temp-pv) that has node affinity to node A, but the deployment has a nodeSelector pointing to node B, causing a volume affinity violation and pods to remain in Pending state. Inject the fault by configuring persistent volumes with node affinity requirements that conflict with pod scheduling.
Tags
Cloud Management System Failure, social-network