Search Results for "elliptical-controller"

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. appmesh-gateway: App Mesh Gateway Helm chart for Kubernetes.

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.

...The community and maintainers of this project and related Kubernetes secret management projects use the #external-secrets channel on the Kubernetes slack for discussion and brainstorming. The project extends the Kubernetes API by adding an ExternalSecrets object using Custom Resource Definition and a controller to implement the behavior of the object itself. An ExternalSecret declares how to fetch the secret data, while the controller converts all ExternalSecrets to Secrets. The conversion is completely transparent to Pods that can access Secrets normally. By default Secrets are not encrypted at rest and are open to attack, either via the etcd server or via backups of etcd data.