News KrakenD CE v2.7 released with better rate-limiting and security options

Community Documentation

Recent changes

You are viewing a previous version of KrakenD Community Edition (v1.4) , go to the latest version

Service Discovery overview

Document updated on Feb 13, 2019

Service discovery enables clients to detect and locate services on your enterprise network automatically. Instead of defining a static list of IPs or hostnames pointing to your backends, you can use a service discovery provider and let KrakenD interact with it to get the hosts dynamically.

Static resolution

The static resolution is the default service discovery choice. It uses a list of hosts declared in the configuration file and KrakenD must be able to reach them directly by hostname, DNS or IP. All the necessary connections are load balanced between all the servers in the list.

Using "sd": "static" in the configuration file is optional.

"backend": [
		"url_pattern": "/some-url",
		"sd": "static",
		"host": [


A typical Service Discovery integration for KrakenD is to use DNS SRV. It is a market standard used by many other systems work such as Kubernetes, Mesos, Haproxy, Nginx plus, AWS ECS, Linkerd, and more.

The most typical setup is KrakenD + Consul (see standard lookup).

See DNS SRV service discovery


There is support for the Netflix Eureka client. The package is an open source contribution via Schibsted engineers.

See Eureka service discovery


Unresolved issues?

The documentation is only a piece of the help you can get! Whether you are looking for Open Source or Enterprise support, see more support channels that can help you.