Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v1.8 backports 2020-12-02 #14249

Merged
merged 6 commits into from
Dec 4, 2020
Merged

v1.8 backports 2020-12-02 #14249

merged 6 commits into from
Dec 4, 2020

Conversation

nathanjsweet
Copy link
Member

@nathanjsweet nathanjsweet commented Dec 2, 2020

v1.8 backports 2020-12-02

Once this PR is merged, you can update the PR labels via:

$ for pr in 14201 14054 14222 14238 14256; do contrib/backporting/set-labels.py $pr done 1.8; done

@nathanjsweet nathanjsweet requested a review from a team as a code owner December 2, 2020 21:33
@maintainer-s-little-helper maintainer-s-little-helper bot added backport/1.8 kind/backports This PR provides functionality previously merged into master. labels Dec 2, 2020
@brb
Copy link
Member

brb commented Dec 2, 2020

@nathanjsweet This comment is probably still relevant #14213 (comment).

brb and others added 4 commits December 2, 2020 17:20
[ upstream commit af6ca19 ]

Previously, insertNeighbor() was assuming that a remote node is in the
same L2 subnet, i.e. directly reachable w/o a gateway. However, this is
not the case for all deployments.

This commit adds a check for detecting whether the remote node is in the
same L2. If it's not, then a gateway IP addr (nexthop) is going to be
arpinged instead of the remote node IP addr.

The missing bit in this commit is a refcounting to avoid redundant arpings
and neigh removals when the gateway is used to access more than one
remote node.

Signed-off-by: Martynas Pumputis <m@lambda.lt>
Signed-off-by: Nate Sweet <nathanjsweet@pm.me>
[ upstream commit b78b3b7 ]

To avoid redundant pings and neigh entry removals when the entry is
still used by other node (happens when two or more nodes can be accessed
through the same gateway).

Signed-off-by: Martynas Pumputis <m@lambda.lt>
Signed-off-by: Nate Sweet <nathanjsweet@pm.me>
[ upstream commit 63f19d2 ]

As reported by #14052, there can be a panic if the configured
DirectRoutingDevice is not included in devices. (InitNodePortAddrs() is
called with option.Config.Devices.)

docs state that:
 If the direct routing device does not exist within devices, Cilium
 will add the device to the latter list.

so this patch adds the device to the list.

Fixes #14052

Signed-off-by: Kornilios Kourtis <kornilios@isovalent.com>
Co-authored-by: Martynas Pumputis <m@lambda.lt>
Signed-off-by: Nate Sweet <nathanjsweet@pm.me>
[ upstream commit 24d4450 ]

This fixes a privileged runtime test failure caused by leaked goroutines on arpings with no response.

Signed-off-by: Jarno Rajahalme <jarno@covalent.io>
Signed-off-by: Nate Sweet <nathanjsweet@pm.me>
@nathanjsweet
Copy link
Member Author

@aanm I'm also going to exclude #14238 from this backport because it became very large.

[ upstream commit 7b0037c ]

This version fixes etcd error "auth token invalid after
watch reconnects" etcd-io/etcd#11954.

Signed-off-by: André Martins <andre@cilium.io>
@aanm
Copy link
Member

aanm commented Dec 3, 2020

@nathanjsweet I've added back in this PR.

@brb can you fix the errors caused by #14201?

Copy link
Contributor

@kkourt kkourt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My patch looks good.

@brb
Copy link
Member

brb commented Dec 3, 2020

@brb can you fix the errors caused by #14201?

@aanm Done. @nathanjsweet Please include #14256 once it has been merged.

[ upstream commit 354d42b ]

/home/travis/gopath/src/github.com/cilium/cilium/pkg/datapath/linux/node_linux_test.go:1096:14:
ineffectual assignment to err

Reported-by: André Martins <andre@cilium.io>
Fix: b78b3b7 ("node: Refcount neighbour entries")
Signed-off-by: Martynas Pumputis <m@lambda.lt>
Signed-off-by: Nate Sweet <nathanjsweet@pm.me>
@aanm
Copy link
Member

aanm commented Dec 3, 2020

test-backport-1.8

@aanm aanm merged commit 4e656b1 into v1.8 Dec 4, 2020
@aanm aanm deleted the pr/v1.8-backport-2020-12-02 branch December 4, 2020 09:41
@aanm aanm mentioned this pull request Dec 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/backports This PR provides functionality previously merged into master.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants