BARCELONA, Spain — April 7, 2022 KrakenD today announced the availability of KrakenD API Gateway in the Microsoft Azure Marketplace, an online store providing applications and services for use on Microsoft Azure. KrakenD customers can now take advantage of the scalability, high availability, and security of Azure, with streamlined deployment and management. The KrakenD API Gateway serves as a unified interface for managing incoming API requests and connecting to the correct destination, while supporting functionalities across security, authorization, traffic management, observability, and load balancing, among other services.

Continue reading →

Read the new documentation This is an article from 2018. You might want to see the Hot reload documentation. A recurrent question when we go around is if KrakenD configuration can be hot-reloaded, this is changing endpoints, backends, or any other configuration of the gateway while it’s running. The short answer is: No, you can’t. You must restart the server. And although we might have something to alleviate this, let us explain first why we don’t support such a feature:

Continue reading →

In this article we are going to show how to configure and deploy the KrakenD API Gateway in a kubernetes environment. We will use for the demonstration Minikube so you cant test it in your own local machine. Let’s get started! Setting up a local Kubernetes We will run Kubernetes locally thanks to Minikube. Just follow the README in the project for the installation and the Quickstart section. Installing minikube it’s quick and easy.

Continue reading →

Everyone loves reaching the maximum number of available platforms for their software but this usually comes at a cost. In this article we will explain how we generated our packaging for Linux in an automated fashion, being faithful to our DevOps dogma. Dockerize all the things! Our dev team uses both Linux and MacOS X in desktop machines and KrakenD has been running and behaving in the same way in all the platforms because from day one we decided to run everything on Docker.

Continue reading →