Load Balancer flavors
For a general tutorial on how to get started with Load Balancers in Kubernetes, please see the Load Balancers guide.
By default, Load Balancers are created with 1G RAM and 1 CPU core. For some use cases this will not be sufficient.
LB provider
Most of our Kubernetes clusters are still configured with the legacy octavia provider, for new clusters we are making the successor to octavia: amphora - the default.
If you need more powerful Load Balancers than the default option mentioned above, we recommend using the amphora provider. To see which one you are currently using you can run the below in your cluster:
kubectl -n kube-system get secret external-openstack-cloud-config -o jsonpath='{.data.cloud\.conf}' | base64 -d - | grep lb-provider
To change lb-provider please create a support case.
Available flavors
lb-provider: amphora
| ID | Name | Specs |
|---|---|---|
| 16cce6f9-9120-4199-8f0a-8a76c21a8536 | v1-lb-1 | 1G, 1 CPU |
| 48ba211c-20f1-4098-9216-d28f3716a305 | v1-lb-2 | 1G, 2 CPU |
| b4a85cd7-abe0-41aa-9928-d15b69770fd4 | v1-lb-4 | 2G, 4 CPU |
| 1161b39a-a947-4af4-9bda-73b341e1ef47 | v1-lb-8 | 4G, 8 CPU |
LEGACY lb-provider: octavia
| ID | Name | Specs |
|---|---|---|
| 4fa90798-b194-4189-981a-4b4856b8e400 | v1-lb-4-octavia | 2G, 4 CPU |
| 0bdfc547-da62-4971-9f07-f6b5f46f5dd2 | v1-lb-8-octavia | 4G, 8 CPU |
Using a flavor
To select a flavor for your Load Balancer, add the below to the Kubernetes Service .metadata.annotations:
loadbalancer.openstack.org/flavor-id: <id-of-your-flavor>
Note that this is a destructive operation when modifying an existing Service, it will remove the current Load Balancer and create a new one (with a new public IP).
Full example configuration for a basic LoadBalancer service:
apiVersion: v1
kind: Service
metadata:
annotations:
loadbalancer.openstack.org/flavor-id: b4a85cd7-abe0-41aa-9928-d15b69770fd4
name: my-loadbalancer
spec:
ports:
- name: http-80
port: 80
protocol: TCP
targetPort: http
selector:
app: my-application
type: LoadBalancer