Performance Analysis of Different Ingress Controllers Within the Kubernetes Cluster

The demand for effective and adaptable traffic routing systems has significantly increased as businesses use container orchestration platforms like Kubernetes. By addressing Kubernetes' intrinsic restrictions on external access, Ingress Controller helps to provide a more reliable, secure, and controllable infrastructure for containerised applications. In Kubernetes, the problem of traffic routing and external access for services inside a cluster is handled by an Ingress Controller. It serves as a specialized layer that controls incoming traffic, offering a declarative and centralized method for load balancing, creating routing rules, and making services visible to the public. The study examines many types of ingress controllers that are out there, each with unique characteristics and functionalities, such as NGNIX, HAProxy, Istio, Traefik and customized ingress controllers. In order for the user to determine which ingress controller will effectively meet the needs of the applications, the study compares a few ingress controllers from the various ingress controller categories based on the features they offer, service response time, and throughput performance.