Furyctl(next) - fix x509 exporter

[nutellinoit]

On behalf of @ralgozino :

After creating a cluster with 3 nodes, going to the dashboard for x509 certificates shows that there are 9 errors in the exporters.

Digging a little more, one can see that each one of the x509 exporters (1 per each node) is logging errors on:

• can’t open /var/lib/kubelet/pki/kubelet-client-current.pem
• can’t open /var/lib/kubelet/pki/kubelet.crt
• can’t open /etc/kubernetes/kubelet.conf

this is because we are on an EKS cluster and these files are managed by AWS and we can’t mount them.

Proposal

Patch x509 exporters in EKS clusters to avoid trying to use these files, so the user does not see misleading errors in the dashboards and in the logs.