You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When two instance of same Kepler versions are deployed on same BM machine and then stress is applied to the machine both Kepler versions report power values that are different from each other.
Attaching below screenshot for reference:
What did you expect to happen?
Since there are no code changes and both Kepler instances are using the same Kepler version ideally they should report the same power values
How can we reproduce it (as minimally and precisely as possible)?
Deploy two versions of Kepler using dev compose manifests
# 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)
The text was updated successfully, but these errors were encountered:
What happened?
When two instance of same Kepler versions are deployed on same BM machine and then stress is applied to the machine both Kepler versions report power values that are different from each other.
Attaching below screenshot for reference:
What did you expect to happen?
Since there are no code changes and both Kepler instances are using the same Kepler version ideally they should report the same power values
How can we reproduce it (as minimally and precisely as possible)?
Anything else we need to know?
No response
Kepler image tag
Kubernetes version
Cloud provider or bare metal
OS version
Install tools
Kepler deployment config
For on kubernetes:
For standalone:
put your Kepler command argument here
Container runtime (CRI) and version (if applicable)
Related plugins (CNI, CSI, ...) and versions (if applicable)
The text was updated successfully, but these errors were encountered: