Last update: Dec 7, 2021
KrakenD operates with its single binary and your associated configuration. Therefore, your build process or CI/CD pipeline only needs to ensure that the configuration file is correct. These are a few recommendations to a safes KrakenD deployment:
FC_OUTas the final artifact
There are several ways to automate KrakenD deployments, but you must always test your configuration before applying it in production. You’ll find a few notes that might help you automate this process in this document.
For the first step, the
check command is a must in any CI/CD pipeline or pre-deploy process to ensure you don’t put a broken setup in production that results in downtime. The
check command lets you find broken configurations before going live. Add a line like the following in your release process:
$krakend check -t -d -c /path/to/krakend.json
The command above will stop the pipeline (
exit 1) if it fails or continue if the configuration is correct. Make sure to always place it in your build/deploy process.
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.