What happened
Google Cloud announced the preview of Fault Injection Testing, a service designed to help developers and architects automate failure testing in cloud environments.
The service supports two primary failure scenarios in this preview: triggering failover of a high availability Cloud SQL instance and degrading application traffic by adding latency and HTTP error codes through a Layer 7 load balancer.
Fault Injection Testing includes an automated dry run before injection, allows manual start, and offers a stop and revert capability to halt experiments and restore resources.
Why it matters
Modern distributed systems are complex, making high availability increasingly difficult to guarantee, especially when direct access to underlying infrastructure is limited in cloud environments.
Without native resilience testing tools, organizations face risks including damaged customer trust, compliance and regulatory penalties, and delays in large-scale migrations.
Running failure experiments before real outages occur helps verify that safety mechanisms work as intended and that mission-critical services remain online during adverse events.
Key facts
Fault Injection Testing is available in preview through the Google Cloud console, the gcloud CLI, and REST APIs.
The service performs a read-only dry run to check permissions and list affected resources before any fault is injected.
Partners such as KeyBank and Servier are already using Fault Injection Testing to validate their deployments.
Google Cloud recommends using Fault Injection Testing in a non-production environment during the preview.
What to watch next
Organizations can request preview access through their Google Cloud Account Team, enable the Fault Testing API, and assign the roles/faulttesting.operator role to run experiments.
During the preview, early users can provide feedback to shape the product, and Google Cloud may expand the supported fault scenarios beyond Cloud SQL failover and load balancer traffic degradation.