1
72%
master: 72%

Ran 04 Jul 2025 07:44AM UTC

Files 27

Run time 0s

Badge

Embed ▾

Committed 04 Jul 2025 07:43AM UTC coverage: 70.891% (+7.7%) from 63.184%

Job # 16068584210.1

Build Type

push

github

Committed by

web-flow

Commit Message

fix: update ingress status only if the load balancer is active (#748)

As per the existing behavior, once the stack update completes, the
ingress controller immediately updates the status of all ingresses and
routegroups to reference the new load balancer. This update may
sometimes happens before the new load balancer has marked its targets
(for example skipper-ingress) as healthy, leading clients being routed to a load
balancer that is not ready to serve traffic yet.

To improve this behavior we retrieve the ELBs via AWS API and build the
models including the ELB states of the corresponding ELBs. Then before
updating the ingresses/routegroups (updateIngress func) we check whether
the ELB is in active state, if not we skip updating the
ingresses/routegroups status with the ELB hostname.

---------

Signed-off-by: Thilina Madumal <thilina.madumal@zalando.de>

Run Details

2752 of 3882 relevant lines covered (70.89%)

10.6 hits per line

zalando-incubator / kube-ingress-aws-controller / 16068584210 / 1
72%
master: 72%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 16068584210.1

zalando-incubator / kube-ingress-aws-controller / 16068584210 / 1 72% master: 72%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 16068584210.1

zalando-incubator / kube-ingress-aws-controller / 16068584210 / 1
72%
master: 72%

README BADGES
x