Email verification tests are small, but their network path is not. A typical CI run starts a pod, calls an application, reaches a mail provider, reads a temporary inbox, and then cleans up the test data. When every one of those connections is allowed by default, a flaky test is hard to explain and an accidental outbound call is easy to miss.
The fix I have found useful is to treat email test traffic as a separate network contract. The test pod gets only the egress it needs, the inbox identity belongs to one CI run, and a blocked connection produces evidence instead of a generic timeout. This is especially helpful when Kubernetes runs inside AWS and several teams share a cluster.
Why email test traffic needs a boundary
An email test normally needs three different paths:
The test runner reaches the application under test.
The application or verifier reaches an approved mail API.
The verifier reads the message and reports the result to CI.
Those paths should not automatically become one broad rule.…