Weave report analyzers #415
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The IPAM pool analyzer checks that utilization of the pod IP subnet is less than 85%. For example, if using 10.32.0.0/12, this analyzer will warn if 3,482 IPs are currently allocated to pods. The pending allocation analyzer checks that the IPAM status in the report has no items for the PendingAllocates field. This indicates the IPAM service is not ready according to the code in the weave status template https://github.com/weaveworks/weave/blob/e3712152d2a0fe3bc998964c948e45bdf8ff6144/prog/weaver/http.go#L186. The weave connections analyzer checks that all connections to remote peers are in the established state. The state will be "pending" if UDP is blocked between nodes and will be "failed" if the weave pod on the remote node is in a crash loop. To force a pending state for testing, run the commands `iptables -A INPUT -p udp --dport 6784 -j REJECT` and `iptables -A INPUT -p udp --dport 6783 -j REJECT` on a peer. The weave connections analyzer also checks that all connections are using the fastdp protocol. A commopn issue seen in the field on CentOS/RHEL 7 is that some sides of a connection are using fastdp and other sides have fallen back to sleeve. Set the WEAVE_NO_FASTDP env var on the weave daemonset to "true" to test this analyzer.
areed
force-pushed
the
areed/weave-analyzer
branch
from
e26bf71
to
91eb94b
Compare
divolgin
approved these changes
Sep 9, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The IPAM pool analyzer checks that utilization of the pod IP subnet is
less than 85%. For example, if using 10.32.0.0/20, this analyzer will
warn if 3,482 IPs are currently allocated to pods.
The pending allocation analyzer checks that the IPAM status in the
report has no items for the PendingAllocates field. This indicates the
IPAM service is not ready according to the code in the weave status
template.
The weave connections analyzer checks that all connections to remote
peers are in the
establishedstate. The state will be "pending" if UDPis blocked between nodes and will be "failed" if the weave pod on the
remote node is in a crash loop. To force a pending state for testing,
run the commands
iptables -A INPUT -p udp --dport 6784 -j REJECTandiptables -A INPUT -p udp --dport 6783 -j REJECTon a peer.The weave connections analyzer also checks that all connections are
using the
fastdpprotocol. A commopn issue seen in the field onCentOS/RHEL 7 is that some sides of a connection are using fastdp and
other sides have fallen back to sleeve. Set the WEAVE_NO_FASTDP env var
on the weave daemonset to "true" to test this analyzer.