Search Results for "haproxy"

Ingress controller implementation for HAProxy loadbalancer. HAProxy Ingress is a Kubernetes ingress controller: it configures a HAProxy instance to route incoming requests from an external network to the in-cluster applications. The routing configurations are built reading specs from the Kubernetes cluster. Updates made to the cluster are applied on the fly to the HAProxy instance.

...Centralized logging - fluentd, logstash or other centralized logging tools that tail the containers JSON log file or files within the container. Log Rotation - logrotate files to rotate container JSON log files. Reverse Proxy Configs - nginx, haproxy, etc. reverse proxy configs to route requests from the host to containers. Service Discovery - Scripts (python, bash, etc..) to register containers within etcd, hipache, etc. Docker-gen can be bundled inside of a container along-side applications. nginx-proxy/nginx-proxy trusted build is an example of running docker-gen within a container along-side nginx. jwilder/docker-register is an example of running docker-gen within a container to do service registration with etcd.

Built in Go, gnet is ultra-fast and memory efficient based on the event-driven mechanism. It's designed to create a networking server framework for Go that performs on par with Redis and Haproxy for networking packets handling. gnet is lock-free during the entire runtime, which keeps gnet free from synchronization issues and speeds it up. gnet provides concise and easy-to-use APIs for users, it only exposes the essential APIs and takes over most of the tough work for users, minimizing the complexity of business code so that developers are able to concentrate on business logic instead of the underlying implementations. gnet supports multiple protocols/IPC mechanism: TCP, UDP and Unix Domain Socket, enabling you to develop a variety of networking applications. gnet is devised as a cross-platform framework, as a result, it works faultlessly on multiple platforms: Linux, FreeBSD, DragonFly BSD, Windows.

...Deploy service mesh within any runtime or infrastructure - Bare Metal, Virtual Machines, and Kubernetes clusters, across any cloud. Resolve discovered services through integrated DNS. Automate 3rd party load balancers (F5, NGINX, HAProxy). Eliminate manual configuration of network devices. Secure services running in any environment leveraging intention based policies and automatic mTLS encryption between service mesh resources. Consul enables detecting the deployment of new services, changes to existing ones, and provides real time agent health to reduce downtime. ...

Voyager is a HAProxy-backed secure L7 and L4 ingress controller for Kubernetes developed by AppsCode. This can be used with any Kubernetes cloud provider including aws, gce, gke, azure, acs. This can also be used with bare metal Kubernetes clusters. Voyager provides L7 and L4 load balancing using a custom Kubernetes Ingress resource. This is built on top of the HAProxy to support high availability, sticky sessions, name and path-based virtual hosting.

...Mesos master running the Marathon and Chronos frameworks. Mesos agent with Docker containerizer. Mesos DNS for core service discovery. Marathon load balancer using HAProxy for SSL and proxying to internal applications. To try it out locally use the Vagrant configuration. To use the scripts to build a custom Mesos cluster first install the roles in your project and configure Ansible to load roles from the roles directory provided by this project. Install the chronos-sync ruby script distributed as part of Chronos. ...