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 Kepler with release-0.7.11 and latest are deployed simultaneously Kepler with latest is underreporting the metric values.
Attaching a comparison screenshot for reference:
Here Kepler using latest has job as dev whereas Kepler using release-0.7.11 has job as latest
What did you expect to happen?
Kepler latest shouldn't under-report the metric values.
How can we reproduce it (as minimally and precisely as possible)?
Deploy Kepler with release-0.7.11 and with latest using dev on a single machine and then compare the metric exported by them. Doing a rate of change between the two will give a good idea.
Anything else we need to know?
No response
Kepler image tag
release-0.7.11, latest
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)
The text was updated successfully, but these errors were encountered:
What happened?
When Kepler with
release-0.7.11
andlatest
are deployed simultaneously Kepler withlatest
is underreporting the metric values.Attaching a comparison screenshot for reference:
Here Kepler using
latest
has job asdev
whereas Kepler usingrelease-0.7.11
has job aslatest
What did you expect to happen?
Kepler latest shouldn't under-report the metric values.
How can we reproduce it (as minimally and precisely as possible)?
Deploy Kepler with
release-0.7.11
and withlatest
usingdev
on a single machine and then compare the metric exported by them. Doing a rate of change between the two will give a good idea.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: