Custom AWS Load Balancer for PubSub+ Cloud
The following information is for customers who configured their EKS cluster using Solace's custom version of the AWS Load Balancer v2.6.1 or earlier. It has been retained for reference purposes only. Solace does not support using Solace's Custom AWS Load Balancer for new cluster creation. For current load balancer requirements, see Load Balancer in the Installing PubSub+ Cloud in Amazon Elastic Kubernetes Service (EKS) documentation.
Solace's version of the AWS Load Balancer Controller v2.6.1 for NLB has optimized ingress. The permissions in the role used by the AWS Load Balancer Controller must be updated to match those specified at https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.2.0/docs/install/iam_policy.json.
Solace's version of the AWS Load Balancer Controller ensures your deployment is not limited to eleven event broker services. Contact Solace if you require repository information and credentials.
Solace has released several versions of the AWS Load Balancer Controller with each version having compatibility with specific Kubernetes releases as follows:
| Solace-specific Release of AWS Load Balancer Controller (tag) | Compatibility with Kubernetes Versions | Link to Permissions for Role |
|---|---|---|
|
v2.2.4-nlb |
1.19, 1.20, 1.21 |
|
|
v2.4.1-nlb |
1.20, 1.21, 1.22, 1.23, 1.24 |
|
|
v2.4.7-nlb |
1.21, 1.22, 1.23, 1.24, 1.25, 1.26 |
|
|
v2.6.1-nlb |
1.27 and later |
Solace configures the Load Balancers with cross-zone load balancing enabled by default. Cross-zone load balancing provides several benefits, including:
- Distributing requests evenly across the event broker services in all of your availability zones.
- Faster fail-over times.
This can come at increased cost due to increased inter-zone bandwidth usage. Having the service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled service annotation set to true enables cross-zone load balancing.