Description
The problem runs on hotel-reservation. Simulate a fault where the liveness probe is too aggressive for services in the hotel reservation application. The deployment `aux-service` has an overly aggressive liveness probe (initialDelaySeconds=0, periodSeconds=1, failureThreshold=1) with terminationGracePeriodSeconds=0, causing pods to be killed immediately if the probe fails. Inject the fault by configuring liveness probes with overly aggressive timeout or failure threshold settings.
Tags
Cloud Management System Failure, hotel-reservation