mirror of
https://github.com/replicatedhq/troubleshoot.git
synced 2026-02-14 18:29:53 +00:00
91eb94baaa
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
e3712152d2/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.
25 lines
546 B
YAML
25 lines
546 B
YAML
apiVersion: troubleshoot.sh/v1beta2
|
|
kind: SupportBundle
|
|
metadata:
|
|
name: collector-sample
|
|
spec:
|
|
collectors:
|
|
- exec:
|
|
collectorName: weave-report
|
|
command:
|
|
- /home/weave/weave
|
|
args:
|
|
- --local
|
|
- report
|
|
containerName: weave
|
|
exclude: ""
|
|
name: kots/kurl/weave
|
|
namespace: kube-system
|
|
selector:
|
|
- name=weave-net
|
|
timeout: 10s
|
|
|
|
analyzers:
|
|
- weaveReport:
|
|
reportFileGlob: kots/kurl/weave/kube-system/*/weave-report-stdout.txt
|