zfy3000163 / heyelb

distributed loadbalancer

HeYe(Parasaus)

HeYe(Parasaus) is a high-performance, high-scalability, ops-friendly, kubernetes-native loadbalancer.

HeYe(Parasaus) provides traffic forward features, which handle traditional north-south traffic, as well as east-west traffic in datacenter efficiently.

The technical architecture of HeYe(Parasaus):

Features

1. The data plane and the control plane are separated in the architecture, a clean architecture is realized. The data plane is borrowed from kubernetes, and the control plane is implemented by ourselves, which is very lightweight.

2. The forward traffic nodes are stateless and support horizontal scaling. The maximum number of nodes is 254, and the computing power and bandwidth are close to infinity.

3. Traffic forwarding is implemented through LVS. As we all know, LVS is an implementation of Layer 4 load balancing inside the Linux kernel. Layer 4 load balancing works on OSI Layer 4 (Transport Layer) and distributes requests to the servers at the transport layer without looking at the content of the packets, so it has the best performance.

4. General x86 server was liked without any special configuration or hardware.

5. The configuration of addition, deletion, modification and query supports hot update, which has no impact on the business. These can be done through yam and API, which is very simple and friendly

6. Supports 3 modes of health check on layer 7 HTTP headers, layer 4 tcp port and mysql service.

7. Supports multiple load balancing modes, such as RR, LC, WLC, WRR, source hash, etc.

Get Started

Scenario 1：cloud-native

Prepare

1. you have to a k8s cluster

Installation

1. configure a volume to store data. for example: nfs, pv&pvc, hostpath

   as following about "hostpath":

   mkdir -p /workdir/servers/ && mkdir -p /workdir/etcd/ && mkdir -p /workdir/kubeconfig/

   cd /workdir/servers/ && touch upstream.conf

   cp your_path/admin.kubeconfig /workdir/kubeconfig/ && cd /workdir/kubeconfig/ && mv admin.kubeconfig kubeconfig.yaml

2. kubectl create -f heyelb/conf/yaml/create_lb.yaml

Scenario 2：traditional datacenter

Prepare

1. core switch supports network quality feature, such as cisco sla, h3c nqa

2. 3 servers， minimal configuration(Strongly recommended):

   • 8c, 32G mem, 100G disk

   • turnoff swap on all nodes，supports passwordless login beetween nodes

Installation

0. equivalent routing is configured on the switch and all traffic which forwards svc_cidr goes through three nodes

1. login node1

2. cd your_path/heyelb/install_cli

3. sh master_node.sh <node2_ip> <node3_ip> <node2_hostname> <node3_hostname> <svc_ip_cidr> <pod_ip_cidr> <etcd_endpoints>

   for example: sh master_node.sh 10.1.1.2 10.1.1.3 k8s02 k8s03 10.1.1.4 10.11.0.0 10.12.0.0 "https://10.1.1.92:2379,https://10.1.1.93:2379,https://10.1.1.150:2379"

4. sh worker_node.sh <etcd_endpoints> <svc_ip_DNS> "cluster.local." "/kube-centos/network"

5. repeat "Scenario 1"

Getting started

1. edit a yaml file, Service.spec.ports.name and Endpoints.subnets.addresses.ports.name must be the same, Endpoints.metadata.annotations.calledSource and Endpoints.metadata.annotations.calledSource.healthCheckType are required.

2. Endpoints.metadata.annotations.calledSource.healthCheckType have 3 types, which supports only http, tcp and mysql.

3. there is a yaml file in /heyelb/example/

ok, let's have a nice journey!

if you have any ideas or questions, please tell me([email protected]) or take a new issue. thanks