Search Results for "controller"

ingress-nginx is an Ingress controller for Kubernetes using NGINX as a reverse proxy and load balancer. It is built around the Kubernetes Ingress resource, using a ConfigMap to store the NGINX configuration. The goal of this Ingress controller is the assembly of a configuration file (nginx.conf). The main implication of this requirement is the need to reload NGINX after any change in the configuration file.

AWS Load Balancer Controller is a controller to help manage Elastic Load Balancers for a Kubernetes cluster. It satisfies Kubernetes Ingress resources by provisioning Application Load Balancers. It satisfies Kubernetes Service resources by provisioning Network Load Balancers. This project was formerly known as "AWS ALB Ingress Controller", we rebranded it to be "AWS Load Balancer Controller".

...Built with production reliability in mind, it uses anycast and health-checking to steer traffic to healthy backends while avoiding single points of failure. It supports common load-balancing policies, NAT, and VIP management, and pairs with standard Linux networking primitives for predictable performance. A controller/worker architecture separates configuration and dataplane concerns, enabling safe rollouts and fast failover. Operators get tooling to define services declaratively and to observe the state of pools, backends, and routes. Seesaw aims to be understandable and operable by network and SRE teams who prefer transparent, Linux-native components over opaque appliances.