Description
The problem runs on social-network. Simulate a fault where the liveness probe is misconfigured for the user-service in the social network application. The deployment `user-service` has a misconfigured liveness probe pointing to a non-existent health endpoint (/healthz on port 8080), causing pods to be restarted repeatedly. Inject the fault by misconfiguring the liveness probe parameters (path, port, or timeout) for the user-service.
Tags
Misconfiguration Failure, social-network