Search Results for "load balancer"

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

Networking plugin for pod networking in Kubernetes using Elastic Network Interfaces on AWS. appmesh-controller: App Mesh controller Helm chart for Kubernetes. appmesh-prometheus: App Mesh Prometheus Helm chart for Kubernetes. appmesh-grafana: App Mesh Grafana Helm chart for Kubernetes. appmesh-jaeger: App Mesh Jaeger Helm chart for Kubernetes. appmesh-spire-server: App Mesh SPIRE Server Helm chart for Kubernetes. appmesh-spire-agent: App Mesh SPIRE Agent Helm chart for Kubernetes....

ExternalDNS synchronizes exposed Kubernetes Services and Ingresses with DNS providers. Inspired by Kubernetes DNS, Kubernetes' cluster-internal DNS server, ExternalDNS makes Kubernetes resources discoverable via public DNS servers. Like KubeDNS, it retrieves a list of resources (Services, Ingresses, etc.) from the Kubernetes API to determine the desired list of DNS records. Unlike KubeDNS, however, it's not a DNS server itself, but merely configures other DNS providers accordingly, e.g. AWS...

...To use the Driver in BI tools, please refer to the documentation. To connect to Amazon Neptune using the JDBC driver, the Neptune instance must be available through an SSH tunnel, load balancer, or the JDBC driver must be deployed in an EC2 instance. SSH Tunnel and host file must be configured before using the drive to connect to Neptune, please see SSH configuration. This driver is compatible with JDBC 4.2 and requires a minimum of Java 8.

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.