Systems | Development | Analytics | API | Testing

The exponential growth of the Internet and cloud computing has given rise to applications that are smaller, more distributed, and designed for highly dynamic environments capable of rapidly scaling up or down as needed. These applications have pushed the demand for modern API management product architectures that can leverage cloud native capabilities to achieve scalability, resilience, agility, and cost efficiency.

Restarting a Kubernetes pod can be necessary to troubleshoot issues, apply configuration changes or simply ensure the pod starts fresh with a clean state. With the power of kubectl, you’ll be able to gracefully restart pods without disrupting the overall application availability. This post will walk you through the process of restarting pods within a Kubernetes cluster using the command-line tool, kubectl. Let’s dive in and learn how to effectively restart Kubernetes pods using kubectl!

In my previous post on scaling Kong deployments with and without a database, we covered the concepts of deploying Kong with and without a database, as well as using decK, distributed, and hybrid deployments. In this article, we take a tour of some of the possible Kubernetes deployments of Kong. Kubernetes (K8s) is the container orchestration war winner. While there are still deployments using other engines, we see K8s far more.