EKS Misconfiguration Scanning Fails

[schuman0]

What steps did you take and what happened:

When running misconfiguration scanning on my EKS clusters it errors out.

What did you expect to happen:

Successfully scans nodes

Anything else you would like to add:

I have tried this with trivy k8s and with running node collector directly and they all fail. The logs from the deployment show:

`E1026 16:01:08.945811 16875 memcache.go:265] couldn't get current server API group list: Get "https://10.100.0.1:443/api?timeout=32s": dial tcp 10.100.0.1:443: i/o timeout
E1026 16:01:38.974453 16875 memcache.go:265] couldn't get current server API group list: Get "https://10.100.0.1:443/api?timeout=32s": dial tcp 10.100.0.1:443: i/o timeout
Error: Get "https://10.100.0.1:443/version": dial tcp 10.100.0.1:443: i/o timeout
Usage:
node-collector k8s [flags]

Flags:
-h, --help help for k8s

Global Flags:
-o, --output string Output format. One of table|json (default "json")
-s, --spec string spec name. default: cis (default "cis")
-v, --version string spec version. default: 1.23 (default "1.23")

Get "https://10.100.0.1:443/version": dial tcp 10.100.0.1:443: i/o timeout`

Environment:

• Trivy-Operator version (use trivy-operator version): 0.16.2
• Kubernetes version (use kubectl version): 1.27
• OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc): Windows/on cluster

[chen-keinan]

@schuman0 can you elaborate on I have tried this with trivy k8s and with running node collector directly its was done not via operator ?