Description
The problem runs on astronomy-shop. Simulate a fault where the DNS policy is incorrectly configured for the frontend service in the astronomy shop application. The deployment `frontend` has a misconfigured DNS policy (set to None with external nameserver 8.8.8.8), causing DNS resolution failures for cluster-internal services. Inject the fault by setting an incorrect dnsPolicy (e.g., Default instead of ClusterFirst) for the frontend service pods.
Tags
Network Failure, astronomy-shop