Closed milandasek-printify closed 7 months ago
/assign @shraddhabang
@oliviassss: GitHub didn't allow me to assign the following users: shraddhabang.
Note that only kubernetes-sigs members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the contributor guide
@milandasek-printify, this already works by setting the service.beta.kubernetes.io/aws-load-balancer-attributes
annotation accordingly, for example like this:
service.beta.kubernetes.io/aws-load-balancer-attributes: dns_record.client_routing_policy=availability_zone_affinity
I also created https://github.com/kubernetes-sigs/aws-load-balancer-controller/pull/3470 to (slightly) improve user experience (input validation).
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
Hello,
When can we expect support for Zone DNS affinity? https://aws.amazon.com/about-aws/whats-new/2023/10/aws-nlb-availability-performance-capabilities/
I guess something like:
service.beta.kubernetes.io/aws-load-balancer-zone-dns-affinity-enabled
Thank you