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.
On empty cluster with no workload traffic (dataplane traffic) with just Weave-net control plane traffic weave-net pods should scale to 100's and even thousands of nodes
What happened?
At cluster size of 200 nodes with sufficient memory and CPU requested for the weave-net pods (to avoid #3593 ), while weaver process does not crash it fails to connects to peers due to various reasons.
As I narrow down the root cause based on the symptoms I will refine the bug accordingly.
How to reproduce it?
Increase CPU and memory requests to 500m and 500 MB so that pods does not crash or OOMKilled and increase the connection limit (CONN_LIMIT) and provision more than 150 nodes
What you expected to happen?
On empty cluster with no workload traffic (dataplane traffic) with just Weave-net control plane traffic weave-net pods should scale to 100's and even thousands of nodes
What happened?
At cluster size of 200 nodes with sufficient memory and CPU requested for the weave-net pods (to avoid #3593 ), while weaver process does not crash it fails to connects to peers due to various reasons.
Logs indicate various sorts of errors as well.
As I narrow down the root cause based on the symptoms I will refine the bug accordingly.
How to reproduce it?
Increase CPU and memory requests to 500m and 500 MB so that pods does not crash or OOMKilled and increase the connection limit (CONN_LIMIT) and provision more than 150 nodes
Versions:
Logs:
The text was updated successfully, but these errors were encountered: