1
53%
master: 53%

Ran 30 Jul 2024 01:08PM UTC

Files 236

Run time 6s

Badge

Embed ▾

Committed 30 Jul 2024 12:44PM UTC coverage: 52.944% (-0.04%) from 52.988%

Job # 10162592982.1

Build Type

Pull #4533

github

Committed by

jcaamano

Commit Message

Get route advertisement information in NAD controller

The network manager running within the NAD controller will, upon
ensuring a network, fetch the VRFs per node a pod network is being
leaked/advertised to from the applicable route advertisements
configuration, and include it in the network information used when
creating a network controller, or triggering a reconciliation if it was
already running.

This relies on annotations set by cluster manager on NADs pointing to
the route advertising configuration that applies to the network which
will come in a future PR/commit.

This includes the default network for which the ever existing default
network controller is used (instead of creating a new network
controller). If necessary, it is assumed that cluster manager will
create a dummy NAD for the default network in ovn-k namespace to set
annotations on. If no NADs for the default network exist or if they have
no annotations, network manager will reconcile the default network to a
default configuration (instead of destroying the network controller).

Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>

Pull Request Pull Request #4533: Direct ingress for default network in SGW mode with route advertisements

Coverage Stats

30056 of 56769 relevant lines covered (52.94%)

97.15 hits per line

ovn-org / ovn-kubernetes / 10162592982 / 1
53%
master: 53%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 10162592982.1

ovn-org / ovn-kubernetes / 10162592982 / 1 53% master: 53%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 10162592982.1

ovn-org / ovn-kubernetes / 10162592982 / 1
53%
master: 53%

README BADGES
x