Iqbal,
You can use KrakenD’s Hot Reload feature to avoid rebuilding and restarting manually after each change. The :watch Docker tag watches your config files and restarts KrakenD automatically when they change, which fits exactly your use case.
To use it, you need to build the :watch image yourself (only for the open source edition) via this repo:
https://github.com/krakend/krakend-watchClone it, then:
docker build -t krakend:watch .
Run it mounting your config folder, for example:
docker run --rm -v "$PWD:/etc/krakend" krakend:watch
There are environment variables to enable flexible configuration if you use those.
Heads up: this feature is only recommended for development. It lacks graceful shutdown, causes some performance loss, and can fail to restart if config is invalid. So it’s not made for production, where config changes should go through version control and CI/CD pipelines.
Check the official docs for detailed setup and usage:
https://www.krakend.io/docs/developer/hot-reload/