You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The above splits traffic between a Kubernetes Service, and an external-provisioned target group, arn:aws:******/external-legecy-tg.
I'm unsure if it would be possible to split between two Kubernetes services. If I interpret the following message correctly, it may not be possible:
The TargetGroups within ForwardConfig have been extended to allow use both Kubernetes Service and TargetGroupArn. Customers can configure backend with Kubernetes Service only / TargetGroupArn only / mix of two(for migration use case)
The text was updated successfully, but these errors were encountered:
Confirmed from implementor that it can target 2+ services:
jessesuen:argo: Today at 11:28 AM @M00nF1sh - does the alb.ingress.kubernetes.io/actions.weighted-routing annotation support the ability to split traffic between two kubernetes services? Or is it only Kubernetes + External ARN?
4 replies
M00nF1sh 15 minutes ago
it supports two kubernetes service(or more) 😄
M00nF1sh 14 minutes ago
basically u can use either ServiceName+ServicePort or ExternalArn in the targetGroups array
Since Rollouts only modifies kubernetes Service objects during canary and doesn't touch AWS Target Groups, would we only support the ServiceName/ServicePort style of TargetGroup definition and not handle TargetGroupArn?
ALB Ingress Controller recently added support for AWS Weighted Target Groups as of their most recent v1.1.5 release.
kubernetes-sigs/aws-load-balancer-controller#1088
The ingress annotation for using weighted target groups look like:
The one-line json for 'weighted-routing' above expands to:
The above splits traffic between a Kubernetes Service, and an external-provisioned target group,
arn:aws:******/external-legecy-tg
.I'm unsure if it would be possible to split between two Kubernetes services. If I interpret the following message correctly, it may not be possible:
The text was updated successfully, but these errors were encountered: