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
{{ message }}
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.
What you expected to happen?
weaver
detects/claims pre-existing IPs attached to theweave
bridge on node viaweave/prog/weaver/reclaim.go
Line 26 in 8c84763
What happened?
weaver
stopped using the host process namespace (via hotsPID) as of #3876, which was needed for detecting devices via the peer ids / process ids here:weave/prog/weaver/reclaim.go
Line 84 in 8c84763
Specifically, given the change of #3876, the following command only detects processes within the PID namespace of the
weave-net
pod:weave/prog/weaver/reclaim.go
Line 79 in 8c84763
How to reproduce it?
weave-net
pod in thekube-system
namespaceweave-net
pod comes back upAnything else we need to know?
This is specifically for
weave
running onk8s
.Versions:
weave version 2.8.1
The text was updated successfully, but these errors were encountered: