Ctrlk
Sign UpGet a DemoContact Us
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Service Discovery

Automatically discover and map services in your infrastructure for targeted chaos engineering

Before you begin, review the following:

How does Harness CE leverage discovered services?

Harness CE uses the discovered services to identify the various available services in the chaos module, that is, the chaos targets in the Kubernetes cluster that you can deploy using Harness or other means.

As an Harness CE user, service discovery simplifies your decision-making around:

  • Which service to target to inject chaos?

  • Which chaos faults to inject into a target service?

  • What validations and health checks to perform while executing chaos faults?

Consequently, you will be able to find the resilience of your service (with the help of resilience coverage reports, service-level resilience scores, and other such metrics).

You can leverage all the permissions mentioned for fault execution as well as service discovery.

Advantages

  • Reduces overhead of creating a database with services

  • User-friendly

  • Increased adoption of Harness CE

When you are onboarding, one of the steps involves discovering services. Harness CE creates the discovery agent that automatically discovers services for your application.

GKE AUTOPILOT COMPATIBILITY

For service discovery on GKE Autopilot clusters, enable the "Use static name for configmap and secret" option during:

  • New discovery agent creation

  • For existing discovery agents

This ensures compatibility with GKE Autopilot's security restrictions. For complete GKE Autopilot setup including chaos engineering, see the GKE Autopilot guide.

Next Steps

PreviousApplication Maps
NextGameDays

Last updated

Was this helpful?