2
39%
master: 39%

Ran 01 Apr 2022 06:48PM UTC

Files 908

Run time 1min

Badge

Embed ▾

Committed 01 Apr 2022 02:51PM UTC coverage: 35.07% (-0.006%) from 35.076%

Job # 40017.2

Build Type

push

travis-ci-com

Committed by

YutaroHayakawa

Commit Message

ipcache: Add test asserting out-of-order Kubernetes events

These tests answer the following questions:

* What happens if we receive an add/ update event from k8s with a pod
  that is using the same IP address of an
  already-gone-pod-but-delete-event-not-received?
* What happens if we receive an delete of an already gone pod after we
  have received an add/ update from a new pod using that same IP
  address?

What these tests confirm is that Kubernetes events that are out-of-order
are handled as they're received. Meaning the ipcache doesn't have any
special logic to handle for example whether an ipcache delete for a pod
X with IP A is the same pod X (by namespace & name) which previously
inserted an ipcache entry.

Suggested-by: André Martins <andre@cilium.io>
Signed-off-by: Chris Tarazi <chris@isovalent.com>

Run Details

45054 of 128470 relevant lines covered (35.07%)

2383.28 hits per line

cilium / cilium / 40017 / 2
39%
master: 39%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 40017.2

cilium / cilium / 40017 / 2 39% master: 39%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 40017.2

cilium / cilium / 40017 / 2
39%
master: 39%

README BADGES
x