Table of Contents
- Packaging sources
- Installing the plugin
- Load the plugin
- Verify loading the plugin
- Removing a plugin
- Distribute your plugin
Custom plugins for Kong consist of Lua source files that need to be in the file system of each of your Kong nodes. This guide will provide you with step-by-step instructions that will make a Kong node aware of your custom plugin(s).
These steps should be applied to each node in your Kong cluster, to ensure the custom plugin(s) are available on each one of them.
You can either use a regular packing strategy (eg.
tar), or use the LuaRocks
package manager to do it for you. We recommend LuaRocks as it is installed
along with Kong when using one of the official distribution packages.
When using LuaRocks, you must create a
rockspec file, which specifies the
package contents. For an example see the Kong plugin
template, for more info about the format see the LuaRocks
documentation on rockspecs.
Pack your rock using the following command (from the plugin repo):
# install it locally (based on the `.rockspec` in the current directory) $ luarocks make # pack the installed rock $ luarocks pack <plugin-name> <version>
Assuming your plugin rockspec is called
kong-plugin-myPlugin-0.1.0-1.rockspec, the above would become;
$ luarocks pack kong-plugin-myPlugin 0.1.0-1
pack command has now created a
.rock file (this is simply a
zip file containing everything needed to install the rock).
If you do not or cannot use LuaRocks, then use
tar to pack the
.lua files of which your plugin consists into a
.tar.gz archive. You can
also include the
.rockspec file if you do have LuaRocks on the target
The contents of this archive should be close to the following:
$ tree <plugin-name> <plugin-name> ├── INSTALL.txt ├── README.md ├── kong │ └── plugins │ └── <plugin-name> │ ├── handler.lua │ └── schema.lua └── <plugin-name>-<version>.rockspec
Installing the plugin
For a Kong node to be able to use the custom plugin, the custom plugin’s Lua sources must be installed on your host’s file system. There are multiple ways of doing so: via LuaRocks, or manually. Choose one, and jump to section 3.
Via LuaRocks from the created ‘rock’
.rockfile is a self contained package that can be installed locally or from a remote server.
luarocksutility is installed in your system (this is likely the case if you used one of the official installation packages), you can install the ‘rock’ in your LuaRocks tree (a directory in which LuaRocks installs Lua modules).
It can be installed by doing:
$ luarocks install <rock-filename>
The filename can be a local name, or any of the supported methods, eg.
Via LuaRocks from the source archive
luarocksutility is installed in your system (this is likely the case if you used one of the official installation packages), you can install the Lua sources in your LuaRocks tree (a directory in which LuaRocks installs Lua modules).
You can do so by changing the current directory to the extracted archive, where the rockspec file is:
$ cd <plugin-name>
And then run the following:
$ luarocks make
This will install the Lua sources in
kong/plugins/<plugin-name>in your system’s LuaRocks tree, where all the Kong sources are already present.
A more conservative way of installing your plugin’s sources is to avoid “polluting” the LuaRocks tree, and instead, point Kong to the directory containing them.
This is done by tweaking the
lua_package_pathproperty of your Kong configuration. Under the hood, this property is an alias to the
LUA_PATHvariable of the Lua VM, if you are familiar with it.
Those properties contain a semicolon-separated list of directories in which to search for Lua sources. It should be set like so in your Kong configuration file:
lua_package_path = /<path-to-plugin-location>/?.lua;;
/<path-to-plugin-location>is the path to the directory containing the extracted archive. It should be the location of the
kongdirectory from the archive.
?is a placeholder that will be replaced by
kong.plugins.<plugin-name>when Kong will try to load your plugin. Do not change it.
;;a placeholder for the “the default Lua path”. Do not change it.
somethingbeing located on the file system such that the handler file is:
The location of the
/usr/local/custom, hence the proper path setup would be:
lua_package_path = /usr/local/custom/?.lua;;
If you wish to install two or more custom plugins this way, you can set the variable to something like:
lua_package_path = /path/to/plugin1/?.lua;/path/to/plugin2/?.lua;;
;is the separator between directories.
;;still means “the default Lua path”.
Note: you can also set this property via its environment variable equivalent:
Reminder: regardless of which method you are using to install your plugin’s sources, you must still do so for each node in your Kong cluster.
Load the plugin
You must now add the custom plugin’s name to the
custom_plugins list in your
Kong configuration (on each Kong node):
custom_plugins = <plugin-name>
If you are using two or more custom plugins, insert commas in between, like so:
custom_plugins = plugin1,plugin2
Note: you can also set this property via its environment variable equivalent:
Reminder: don’t forget to update the
custom_plugins directive for each node
in your Kong cluster.
Verify loading the plugin
You should now be able to start Kong without any issue. Consult your custom plugin’s instructions on how to enable/configure your plugin on an API or Consumer object.
To make sure your plugin is being loaded by Kong, you can start Kong with a
debug log level:
log_level = debug
Then, you should see the following log for each plugin being loaded:
[debug] Loading plugin <plugin-name>
Removing a plugin
There are three steps to completely remove a plugin.
Remove the plugin from your Kong api configuration. Make sure that it is no longer applied globally nor for any API or consumer. This has to be done only once for the entire Kong cluster, no restart/reload required. This step in itself will make that the plugin is no longer in use. But it remains available and it is still possible to re-apply the plugin.
Remove the plugin from the
custom_pluginsdirective (on each Kong node). Make sure to have completed step 1 before doing so. After this step it will be impossible for anyone to re-apply the plugin to any Kong api, consumer, or even globally. This step requires to restart/reload the Kong node to take effect.
To remove the plugin thoroughly, delete the plugin-related files from each of the Kong nodes. Make sure to have completed step 2, including restarting/reloading Kong, before deleting the files. If you used LuaRocks to install the plugin, you can do
luarocks remove <plugin-name>to remove it.
Distribute your plugin
The preferred way to do so is to use Luarocks, a package manager for Lua modules. It calls such modules “rocks”. Your module does not have to live inside the Kong repository, but it can be if that’s how you’d like to maintain your Kong setup.
By defining your modules (and their eventual dependencies) in a rockspec file, you can install those modules on your platform via Luarocks. You can also upload your module on Luarocks and make it available to everyone!
Here is an example rockspec which would use the “builtin” build type to define modules in Lua notation and their corresponding file:
Kong can fail to start because of a misconfigured custom plugin for several reasons:
“plugin is in use but not enabled” -> You configured a custom plugin from another node, and that the plugin configuration is in the database, but the current node you are trying to start does not have it in its
custom_pluginsdirective. To resolve, add the plugin’s name to the node’s
“plugin is enabled but not installed” -> The plugin’s name is present in the
custom_pluginsdirective, but that Kong is unable to load the
handler.luasource file from the file system. To resolve, make sure that the lua_package_path directive is properly set to load this plugin’s Lua sources.
“no configuration schema found for plugin” -> The plugin is installed, enabled in custom_plugins, but Kong is unable to load the
schema.luasource file from the file system. To resolve, make sure that the
schema.luafile is present alongside the plugin’s