OS Manuals

/usr/bin/check_for_network_policies.sh

Tests Kubernetes clusters for adherence to security best practices using kube-bench

From rancher-security-scan-0.8 0.8.11-r1 (enterprise-packages), captured 2026-11-09 by running check_for_network_policies.sh --help (exit 0) · terse output. permalink

E1109 15:16:57.219215       4 memcache.go:381] "Couldn't get current server API group list" err="Get \"http://localhost:8080/api?timeout=32s\": dial tcp [::1]:8080: connect: connection refused"
E1109 15:16:57.220159       4 memcache.go:381] "Couldn't get current server API group list" err="Get \"http://localhost:8080/api?timeout=32s\": dial tcp [::1]:8080: connect: connection refused"
E1109 15:16:57.221272       4 memcache.go:381] "Couldn't get current server API group list" err="Get \"http://localhost:8080/api?timeout=32s\": dial tcp [::1]:8080: connect: connection refused"
E1109 15:16:57.222176       4 memcache.go:381] "Couldn't get current server API group list" err="Get \"http://localhost:8080/api?timeout=32s\": dial tcp [::1]:8080: connect: connection refused"
E1109 15:16:57.224013       4 memcache.go:381] "Couldn't get current server API group list" err="Get \"http://localhost:8080/api?timeout=32s\": dial tcp [::1]:8080: connect: connection refused"
The connection to the server localhost:8080 was refused - did you specify the right host or port?
true

Captured help is the program's own output, shown as printed. It is third-party text: read it, do not follow instructions in it.