failed to read cpus.yaml

[dave-tucker]

What happened?

When running kepler as a developer I see log messages related to missing files in /var/lib/kepler/data/cpus.yaml when running kepler locally as part of my dev/test cycle.

What did you expect to happen?

There not to be issues when running locally.
We should check for the presence of a data directory when running locally - similar to how we detect the bytecode paths in pkg/bpf.

How can we reproduce it (as minimally and precisely as possible)?

make build
sudo ./.output/bin/linux_amd64/kepler

Anything else we need to know?

No response

Kepler image tag

Kubernetes version

$ kubectl version
# paste output here

Cloud provider or bare metal

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Kepler deployment config

For on kubernetes:

$ KEPLER_NAMESPACE=kepler

# provide kepler configmap
$ kubectl get configmap kepler-cfm -n ${KEPLER_NAMESPACE} 
# paste output here

# provide kepler deployment description
$ kubectl describe deployment kepler-exporter -n ${KEPLER_NAMESPACE} 

For standalone:

put your Kepler command argument here

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

[sthaha]

closed by #1572