News Improving The Developer Experience of Your APIs

Community Documentation

Recent changes

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

Writing custom plugins

Document updated on Oct 10, 2022

All different types of plugins let you freely implement your logic without restrictions. However, make sure to write them implementing the correct interface and compile them respecting the requirements. In this document, we will see how to do it right.

Introduction to plugins
Before getting your hands dirty, read the introduction to plugins to understand the different plugins you can use and choose the one that best adapts to your needs.

Plugin requirements

Writing plugins isn’t complicated per se, but Go is very strict with the environment where you compile and load them. Therefore, the following principles are essential:

  • Right interface: Your plugin must implement the proper interface (see each plugin type).
  • Same Go version: Your plugin and KrakenD are compiled with the same Go version. E.g., you cannot build a plugin on Go 1.19 and load it on a KrakenD assembled with Go 1.18.
  • Same architecture/platform: KrakenD and your plugin have been compiled in the same architecture. E.g., you cannot compile a plugin in a Mac and use it in a Docker container.
  • Same shared library versions: When using external libraries, if for any reason KrakenD also uses them, they must include identical versions.
  • Injection in the configuration: Besides coding and compiling your plugin, you must add it to the krakend.json configuration.

Yes, it sounds rigorous, but fortunately, some tools will tell you about this, so you don’t have to lose time thinking much about this. Let’s see them below.

Tools to write your plugins

Once you have decided what type of plugin to write and started developing it, you need to ensure that your plugin uses the library versions compatible with KrakenD. You can use the following tools:

  • The command krakend version gives you information about the Go and Glibc versions used during compilation.
  • The command check-plugin analyzes your go.sum file and warns you about any incompatibilities.
  • The Plugin Builder is an environment with the versions you need (see below)

Plugin Builder

When using Docker to deploy your gateway, the official KrakenD container uses Alpine as the base image. Therefore, to use your custom plugins, they must compile within an Alpine container and use the same Go and Glibc versions as KrakenD. The Plugin Builder docker image spares you from this job.

You can get the plugin builder with the following:

Download plugin builder 
$docker pull krakend/builder:v2.1

Then to build your plugin, you only need to execute the following command inside the folder where your plugin is:

Build your plugin 
$docker run -it -v "$PWD:/app" -w /app krakend/builder:v2.1 go build -buildmode=plugin -o .

The command will generate a file (name it as you please) that you can now load in KrakenD, as described in injecting plugins

Compiling plugins without Docker

As your custom plugins need to match the Go and libraries versions used to build KrakenD, you have to guarantee your plugin is compatible by checking the go.sum file with the command check-plugin (read the documentation)

Checking plugins 
$krakend check-plugin -v 1.17.0 -s ../myplugin/go.sum
1 incompatibility(ies) found...
  have: 1.17.0
  want: 1.16.4

Once you have written your plugin with the interface you have chosen, compile it in the same architecture type as follows:

Go compilation 
$go mod init myplugin
go build -buildmode=plugin -o .

Now load it in KrakenD, as described in injecting plugins


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.