Proxy-scanner - Failed to connect to lacework-scanner-proxy-scanner.lacework.svc.cluster.local port 8080 after 3 ms: Connection refused

[shyamjos]

After deploying the proxy scanner using the official helm chart we are unable to do an on-demand scan, getting connection refused error, from the logs we can see that server is listening on port 8080 but not responding when we curl the service

image version 0.9.0

Proxy scanner logs

[WARNING]:   2022-09-20 07:15:08 - Error while loading cache file. Scanner will start with bootstap mode: open /opt/lacework/lacework_proxy_scanner_state.json.gz: no such file or directory 
[ERROR]:   2022-09-20 07:15:08 - Error while loading cache. Running in bootstrap mode. open /opt/lacework/lacework_proxy_scanner_state.json.gz: no such file or directory 
[INFO]:   2022-09-20 07:15:13 - Starting server.. 
[INFO]:   2022-09-20 07:15:13 - ScanDataHandlerWorker #1: Starting.. 
[INFO]:   2022-09-20 07:15:13 - RegistryScannerWorkers #0: Starting.. 
[INFO]:   2022-09-20 07:15:13 - Listener started 
[INFO]:   2022-09-20 07:15:13 - server started successfully on port 8080 

curl output

curl lacework-scanner-proxy-scanner.lacework.svc.cluster.local:8080
curl: (7) Failed to connect to lacework-scanner-proxy-scanner.lacework.svc.cluster.local port 8080 after 3 ms: Connection refused

[shyamjos]

We fixed this issue, If the .Values.name is defined and the user passes release name via helm cli , then we should set selector as {{ include "scanner.fullname" . }} otherwise service will become inaccessible.

Also created a PR #112