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
At this moment argo rollouts spec with alb plugin supports several ingresses, but doesn't support several ports for k8s services. This is a problem, because there are lots of use cases when k8s service has several ports:
Use Cases
In our setup we have several ingresses pointed at the same load balancer via alb.ingress.kubernetes.io/group.name annotation and each ingress has an underlying k8s service with a specific port (k8s service is the same for the business service), example:
Given the fact that the rollout spec should include all ingresses for the application and in case you have several ports being listened there is a problem with canary:
i have also same use case for internal and external ALB's on same rollout. It would be nice to add support for service ports per each ingress so canary could be used for all of them.
Summary
At this moment argo rollouts spec with alb plugin supports several ingresses, but doesn't support several ports for k8s services. This is a problem, because there are lots of use cases when k8s service has several ports:
![Screenshot 2023-10-26 at 18 05 47](https://private-user-images.githubusercontent.com/43088906/278405995-8e8a1130-48d7-4d88-9233-6bd758774549.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk2NzY0MDcsIm5iZiI6MTczOTY3NjEwNywicGF0aCI6Ii80MzA4ODkwNi8yNzg0MDU5OTUtOGU4YTExMzAtNDhkNy00ZDg4LTkyMzMtNmJkNzU4Nzc0NTQ5LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjE2VDAzMjE0N1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTlmOTU0YzEzZGZmOGRlMGQ1MDZmYTNhZjc0MTlmM2I3YTY4ZjIzMDAzY2M5OTMyMDgxMWNiNDQ3ZDI3YjljMDcmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.Ch1N7O7UCMC0HFkr-CnsRcMbJRfAHfZYKly0WItS0hU)
Use Cases
In our setup we have several ingresses pointed at the same load balancer via
alb.ingress.kubernetes.io/group.name
annotation and each ingress has an underlying k8s service with a specific port (k8s service is the same for the business service), example:ingress №1:
ingress №2:
Given the fact that the rollout spec should include all ingresses for the application and in case you have several ports being listened there is a problem with canary:
It would be nice to add support for service ports per each ingress so canary could be used for all of them.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered: