Using Loxi LB to provision Load Balancers for a Kubernetes Cluster

[bewdycodebase]

So the idea was to deploy loxiLB with the below behavior

Watches kubernetes cluster for LoadBalancer service types

Assigns a publicly assignable public IP to the LoadBalancer in kubernetes

Currently loxiLB assigns the LoadBalancer a non public IP address and then the LoadBalancer can be accessed using the loxiLB Node IP at a specific port

Issue with is that I cannot directly register an A name with an IP like 1.1.1.1:50004 were 1.1.1.1 is the IP of the node where loxiLB is hosted

Has anyone done something similar?

[inhogog2]

Hi @bewdycodebase ,

It is also possible to register a public IP address directly using "loxilb.io/staticIP" annotation.

Below is an example of "loxilb.io/staticIP", so you can use the staticIP annotation.

apiVersion: v1
kind: Service
metadata:
  name: sctp-lb-fullnat
  annotations:
    loxilb.io/lbmode: "fullnat"
    loxilb.io/staticIP: "1.1.1.1"
spec:
  loadBalancerClass: loxilb.io/loxilb
  externalTrafficPolicy: Local
  selector:
    what: sctp-fullnat-test
  ports:
   - port: 50004
     protocol: SCTP
     targetPort: 9999
  type: LoadBalancer

[backguynn]

LoxiLB can use either a public or private IP as the external IP for the loadBalancer service. The key point is whether incoming traffic from external sources can reach LoxiLB with the external IP of loadBalancer service as the destination.

In LoxiLB's example documents that are based on an AWS environment, the private IP of a node is assigned as the external IP for the LoadBalancer service. The reason for this is that when external traffic is sent to a node, the destination IP is NATed from a public IP to a private IP. Therefore, in this case, LoxiLB uses a private IP as the external IP, but it can still be accessed via the public IP.

[TrekkieCoder]

If you check this doc , there is a special CIDR - --externalCIDR=0.0.0.0/32 which can be used in kube-loxilb manifest file. With this loxilb will automatically accept any traffic destined to its privateIP address. You can then simply add an A record to its publicIP and it should be done. There is also an automated way of supporting this whole process but only in AWS/EKS.