AWS ALB header based routing support

[joey100]

Summary

We have scenarios that the ALB can route traffic to different target groups(canary/stable services) based on request headers. It seems ALB itself can do this, using ALB ingress annotation or modify the ALB listen rules on AWS console. However, I don't see that Argo Rollouts can support AWS ALB with this header based routing.
The rollout spec doc explains that rollout controller injects the alb.ingress.kubernetes.io/actions. annotation, containing a JSON payload understood by the AWS Load Balancer Controller, directing it to split traffic between the canaryService and stableService according to the current canary weight.
Looks like it's the only way of managing traffic with ALB.

Do you have any example of how the rollout spec should be like to support header based routing with ALB or it's not supported yet?

I understand rollout supports header based routing with Istio, but how about ALB?

rgo Rollouts has ability to send all traffic to the canary-service based on a http request header value. Right now it's implemented for the Istio only.

What change needs making?

Use Cases

We have scenarios that the ALB can route traffic to different target groups(canary/stable services) based on request headers.

When would you use this?
Now.

---

Message from the maintainers:

Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.

[zachaller]

This feature is being worked on. #2061

[github-actions]

This issue is stale because it has been open 60 days with no activity.

[github-actions]

This issue is stale because it has been open 60 days with no activity.

[zachaller]

Completed and merged

[joey100]

Hi @zachaller @perenesenko Thanks a lot for the ALB header based routing support, it works!

However, I see the current workflow is that we can make a specific subset of users(custom-header:xxx) access canary version all the time, and the others access stable version and canary version based on the ratio.

May I know if there is possibility that a specific subset of users access canary version all the time, and the others access stable version all the time?

P.S: all the time means during canary deployment, from canary step 1 to the last step.

[zachaller]

It sounds like you just want to not use any setWeight steps in your rollout?

[joey100]

It sounds like you just want to not use any setWeight steps in your rollout?

Hi @zachaller Yes, but there is new question: how can I set the canary version pods? Because if we use setWeight steps at least the canary pod numbers will be adjusted accordingly.

[zachaller]

This should help you https://argo-rollouts.readthedocs.io/en/stable/features/canary/#dynamic-canary-scale-with-traffic-routing

[felixrb86]

hi @joey100 , can you show me what did you do for the ALB header based routing using Argo Rollout and Istio?