Allow to canary endpoint feature to support mupliple AWS ALB. #709

[jukops]

Summary

Our application has 2 ALBs. but looks support only an ALB. I'm using alb ingress controller for mapping between ingress and AWS ALB.

• currently yaml.
  Only that app-ext ingress can receive canary traffic when deployment. Other ingress(ALB) which is connected to app pods should receive stable traffic as 100% when deployment.

  strategy:
    canary:
      canaryService: app-canary
      stableService: app-stable
      trafficRouting:
        alb:
          ingress: app-ext
          servicePort: 80
      steps:
      - setWeight: 5
      - pause: {}

Use Cases

Our app has internal alb for VPC internal connection and has external alb for enduser(client). so required multiple ALBs.

---

Message from the maintainers:

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

[jessesuen]

Our app has internal alb for VPC internal connection and has external alb for enduser(client). so required multiple ALBs.

I think this use case makes sense to support multiple alb ingress references.

[jukops]

Our app has internal alb for VPC internal connection and has external alb for enduser(client). so required multiple ALBs.

I think this use case makes sense to support multiple alb ingress references.

Thanks for kindly reply.
Actually, This is the feature that I need. But I cannot attach multiple ALB now :( I'm using only an ALB due to this problem.
If it's implemented, It would be really good.

[allupaku]

Do you think a definition like this would suffice this use case ?

strategy:
    canary:
      canaryService: app-canary
      stableService: app-stable
      trafficRouting:
        alb:
          - ingress: app-ext
            servicePort: 443
         - ingress: app-interal
            servicePort: 80

[n888]

@allupaku that looks good to me 👍

Currently working around this by deploying 1 Rollout per ALB, and then each Rollout is promoted individually.

Small request: Could we fix the typo in the issue title?

[github-actions]

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

[zachaller]

Closing in favor of #2471 becuase of the added patch