Systems | Development | Analytics | API | Testing

Gateway to the Future: Kong Ingress Controller 3.0

The Kubernetes Gateway API is the future of Kubernetes networking, and Kong are all-in. Kong Ingress Controller (KIC) was the first ingress controller to submit a conformance profile, and we continue to lead the pack. KIC 3.0 adds official support for the Gateway API and makes it the default way to configure Kong Gateway on Kubernetes.

What is Kubernetes CrashLoopBackOff error, and how to fix it?

Kubernetes is one of the most popular container orchestration platforms. It helps with automated deployment, scaling, and management of containerized applications. But sometimes, it experiences some turbulences - as in a CrashLoopBackOff Error. Calling it an error is not entirely right. It expresses a state of restart loop happening somewhere in the background, i.e., in a pod.

Kubernetes Gateway API: an Engineering Perspective

The Kubernetes Gateway API represents a massive collaborative effort and key advancement in Kubernetes networking. Developed by multiple vendors and community members, the Gateway API provides a robust and extensible new standard for managing ingress traffic. With the recent general availability of version 1.0.0, the Gateway API is now ready for production use. The release of the Gateway API is a major milestone for Kubernetes networking that has the potential to simplify and enhance ingress management.

Understanding Dreamfactory's Docker and Kubernetes Pricing Model

We’re excited to unveil our brand-new Docker and Kubernetes offerings, specifically tailored to give you more flexibility, scalability, and options to manage and deploy your software. As always, transparency is a cornerstone of our relationship with our customers. To ensure clarity, we’ve put together this guide to help you understand our pricing structure for these offerings.

Gateway API: From Early Years to GA

In the Kubernetes world, the Ingress API has been the longstanding staple for getting access to your Services from outside your cluster network. Ingress has served us well over the years and can be found present in several dozen different implementations, but as time has passed and Kubernetes has grown it's become clear that there exists a greater need than Ingress is able to deliver.

Why We Love the Gateway API

Kubernetes took the world by storm in 2014. A CLI-first experience, containers as a first-class citizen, and a need to dynamically scale workloads meant that Kubernetes was the right choice for many teams moving to the cloud. By late 2015, the community realized that there needed to be a standard way to manage traffic at the edge of a cluster and so the Ingress API was born.

Kubernetes Sidecar Container - Best Practices and Examples

An open-source container management engine called Kubernetes is used to automatically launch, scale, and handle containerized apps. The fundamental unit of a Kubernetes program is a pod. Instead of managing containers, Kubernetes controls pods, and pods enclose containers. A number of containers, storage, IP addresses, and settings that control how containers should operate inside the pod can all be found in a pod. You can operate two closely linked containers together with sidecar containers.