traffic routing by alb and nginx simultaneously is not working

[fabioviana-hotmart]

Checklist:

• I've included steps to reproduce the bug.
• I've included the version of argo rollouts.

Describe the bug

I have an application with three ingresses. One of them is an ALB and the others are NGINX. I've tried to migrate it to argo rollouts with this manifest below:

apiVersion: argoproj.io/v1alpha1
kind: Rollout
metadata:
  name: sample-api
  labels:
    app: sample-api
spec:
  replicas: 2
  workloadRef:
    apiVersion: apps/v1
    kind: Deployment
    name: sample-api
  analysis:
    successfulRunHistoryLimit: 3
    unsuccessfulRunHistoryLimit: 3
  strategy:
    canary:
      stableService: sample-api
      canaryService: sample-api-canary
      trafficRouting:
        alb:
          ingresses:
          - sample-api-alb
          servicePort: 80
          rootService: sample-api-root
        nginx:
          stableIngresses:
          - sample-api-public
          - sample-api-internal
          canaryIngressAnnotations:
            provider: canary
      steps:
      - setWeight: 10
      - pause:
          duration: 5m
      - setWeight: 30
      - pause: {}

When argo rollouts tries to reconciliate this configurations it emits this error:

spec.strategy.canary.trafficRouting.nginx.stableIngress: Invalid value: \"\": ingress `sample-api-alb` has no rules using service sample-api backend

But there isn't a definition for stableIngress in my nginx statement, just stableIngresses instead, much less with an ingress called sample-api-alb. It's configured just on alb statement.

To Reproduce

1. Create an alb ingress and one or more nginx ingress for the same application
2. Configure a rollout with both ingresses, each one in its trafficRouting statement
3. Apply the rollout and you will see the error

Expected behavior

Both ingresses traffic managed by argo rollouts simultaneously.

Version

v1.8.3

Logs

time="2025-09-17T01:50:50Z" level=error msg="spec.strategy.canary.trafficRouting.nginx.stableIngress: Invalid value: \"\": ingress `sample-api-alb` has no rules using service sample-api backend" error="<nil>"

---

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

[puretension]

Hi @fabioviana-hotmart,

Sorry for accidentally linking a commit to this issue earlier - I was testing a potential fix and made a mistake with the commit message.

I've analyzed your issue and I believe I understand the problem. The validation logic incorrectly checks your ALB ingress (sample-api-alb) against NGINX validation rules, even though it should only validate NGINX ingresses (sample-api-public, sample-api-internal).

Would you be interested in a fix that modifies the validation logic to properly distinguish between ALB and NGINX ingresses when both are configured simultaneously?

I can prepare a proper solution if this approach sounds correct to you.

[fabioviana-hotmart]

@puretension yes, I would... it's exactly you've understood and thanks for help me with this issue.

[puretension]

Thanks a lot for giving me the chance to work on this. 🙏
I’ll put my best effort into delivering a proper fix so that ALB and NGINX traffic routing can work smoothly together.😄