Google Cloud FIT: Break Things on Purpose, Before They Break You

When databases fail and network paths falter, your mission-critical services need to stay online. But modern distributed systems are tangled like a swamp full of water-weed—complex and hard to predict. That’s why Google Cloud just launched Fault Injection Testing (FIT) in preview, a native tool to help you automate failure testing and keep your services swimming smoothly.

FIT lets you deliberately inject faults into your environment, so you can verify your safety mechanisms before a real outage hits your customers. Think of it as a controlled swamp-dive: you know the caimans are lurking, but you’re testing the waters with a net.

Why Native Resilience Testing Matters

In self-hosted data centers, you have direct access to infrastructure for failover testing. In the cloud, that access is limited—so without native tools, you’re flying blind. That gap exposes you to serious risks:

• Damaged trust and reputation: Frequent failures or poor performance lead to customer dissatisfaction and long-term brand damage.
• Compliance and regulatory penalties: Industries like finance must prove disaster recovery capabilities or face audits and fines.
• Migration delays: Large-scale migrations stall when teams can’t verify stability during a zone failure.

How FIT Works

FIT runs experiments using templates—blueprints that define the fault to inject and the resources to target. In this preview, you can test two primary scenarios:

• Failover Cloud SQL: Triggers a failover of a high availability Cloud SQL instance from primary to standby zone.
• Degrade application traffic: Adds latency and HTTP error codes through a Layer 7 load balancer.

Before any fault is injected, FIT performs an automated dry run—a read-only simulation that checks permissions and lists every affected resource. Once you verify the scope, you can start the injection manually. The fault runs for the duration you set, then reverts automatically. If things go sideways, you can stop and revert immediately.

During preview, best practice is to use FIT in a non-production environment. It’s a chance to learn how the service fits your existing testing practices and to give feedback.

Built for the Enterprise

Partners like KeyBank and Servier are already using Cloud FIT to validate deployments. By simulating zonal outages, they ensure their services remain stable—no surprise caiman attacks.

Get Started with Cloud FIT

FIT is available through the Google Cloud console, the gcloud CLI, and REST APIs. Here’s how to dive in:

1. Request preview access: Talk to your Google Cloud Account Team to add your project.
2. Enable the API: Search for “Fault Testing API” in your console and enable it.
3. Assign roles: Ensure your team has roles/faulttesting.operator to configure and run experiments.
4. Run your first dry run: Create a template for a Cloud SQL or load balancer resource in a non-production environment.

For more details, check the User Guide for FIT. And if you’re exploring resilience strategies, our Google Cloud review and Neon Database review might help you pick the right tools for your swamp.

Original announcement published on Google Cloud.