Listener weights and per-cluster target registration

Listener weights and per-cluster target registration An architecture diagram generated by Archify. Client · New connections · Architecture component Client New connections ALB / NLB · Weighted forward action · Architecture component ALB / NLB Weighted forward action Target Group A · weight 20 · Architecture component Target Group A weight 20 Target Group C · weight 80 · Architecture component Target Group C weight 80 Cluster A workers · Pod registration by TGB · AZ-a Cluster A workers Pod registration by TGB Cluster C workers · Pod registration by TGB · AZ-c Cluster C workers Pod registration by TGB Requests 20 / 100 80 / 100 Pod targets Pod targets AZ-a AZ-c Legend Backend Cloud External

Configuration ownership

  • • Manage LB and target groups through external IaC
  • • TGB registers targets; it has no weight field
  • • For nondefault ALB rules, modify that rule’s action

Verify the transition

  • • Weight zero can close existing connections; test reconnection
  • • Check NewFlowCount, ActiveFlowCount, and health
  • • Validate AZ target placement and cross-zone settings

DNS and recovery

  • • Route 53 selects LB endpoints, not target-group ARNs
  • • EKS zonal shift does not rewrite cross-cluster weights
  • • Configure autoshift and healthy-cell capacity separately