I cannot make HAZL work on EKS

Linkerd General Discussion
1

It seems that in order to work I need

  • Kubernetes cluster with three zone-labeled nodes (zone-0 zone-1 zone-2)
  • [Buoyant Enterprise for Linkerd] installed
  • The BUOYANT_LICENSE environment variable set, with functioning BEL CLI

I created new node labels with topology.kubernetes.io/zone=zone-[0 1 2].

However, I noticed that node labels are still topology.kubernetes.io/zone=us-west-2[a b c].

Is there a way to change the label?

Best,

Bruno

1 Like
2

Hi Bruno,

AKS, EKS, and clusters provided by CSPs generally enforce their own topology on the nodes. The following is an example using AKS.

$ kubectl get nodes --show-labels | grep topology.kubernetes.io/zone
aks-hazlpoolha-33634351-vmss000000   Ready    <none>   33h     v1.29.8   agentpool=hazlpoolha,...topology.kubernetes.io/zone=koreacentral-1
aks-hazlpoolha-33634351-vmss000001   Ready    <none>   33h     v1.29.8   agentpool=hazlpoolha,...topology.kubernetes.io/zone=koreacentral-2
aks-hazlpoolha-33634351-vmss000002   Ready    <none>   7m16s   v1.29.8   agentpool=hazlpoolha,...topology.kubernetes.io/zone=koreacentral-3

However, it’s not mandatory to use zone-labeled nodes (e.g., zone-0, zone-1, zone-2). The zone label requirement is primarily for deploying the colorz application as-is, as detailed here: Buoyant HAZL documentation, and HAZL work with different labels, as long as the pods are in separate nodes.

You can find an example of HAZL deployment using different topology labels here: HAZL Deployment Example.

3

Does HAZL deactivate itself (silently with no log indications) if I have more than 100 pods with a free license?