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".

...It allows the modification of the requests and responses with filters that are independently configured for each route. Skipper can be used to run as a Kubernetes Ingress controller. Details with examples of Skipper’s capabilities and an overview can be found in the ingress-controller deployment docs.

kubectl tree is a kubectl plugin that lets you visualize Kubernetes object hierarchies as a tree by following the ownerReferences set on API objects. Instead of manually chasing which ReplicaSet owns which Pods or which higher-level controller is responsible for a given resource, it prints an ASCII tree that shows parent-child relationships at a glance. This is especially useful for understanding how complex workloads like Deployments, StatefulSets, Knative Services, or Agones Fleets fan out into lower-level resources across the cluster. The plugin is written in Go, packaged for easy installation via the krew plugin manager, and exposes flags to control namespace scoping, label selectors, and condition filters so you can narrow what’s shown. ...

GLBC is a GCE L7 load balancer controller that manages external loadbalancers configured through the Kubernetes Ingress API. Ingress exposes HTTP and HTTPS routes from outside the cluster to services within the cluster. Traffic routing is controlled by rules defined on the Ingress resource. An Ingress may be configured to give Services externally-reachable URLs, load balance traffic, terminate SSL / TLS, and offer name-based virtual hosting.

...Install the The CoreDNS multicluster plugin into each participating cluster. The multicluster plugin enables CoreDNS to lifecycle manage DNS records for ServiceImport objects. The controller must have sufficient IAM permissions to perform required Cloud Map operations. Grant IAM access rights AWSCloudMapFullAccess to the controller Service Account to enable the controller to manage Cloud Map resources.