Kubernetes monitoring: wrong cpu and memory limits retrieved

XMLWordPrintable

    • Type: Problem report
    • Resolution: Unresolved
    • Priority: Trivial
    • None
    • Affects Version/s: 6.4.4
    • Component/s: Templates (T)
    • Environment:
      Zabbix standalone 6.4.4 on Debian. Kubernetes zabbix template 6.4.0. Kubernetes 1.24.11

      Steps to reproduce:

      1. I have got a kubernetes cluster of 3 master nodes and 3 worker nodes.
      2. Install kubernetes zabbix template "Kubernetes nodes by HTTP"
      3. Open most recent data for memory/cpu limit of specific node. Example: kube.node.limits.memory[k8s-worker-p02]

      Result:
      Should see the exact same limit values from this command:

      kubectl describe node k8s-worker-p02 | grep -A 10 "Allocated resources"

      Expected:
      But there is a slight difference in the value.

      See the images below.

      MEMORY: 34640 MB is different than 35.61 GB
      CPU: 16 is different than 25

       

            Assignee:
            Zabbix Integration Team
            Reporter:
            Bruno Guimarães Sousa
            Votes:
            3 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: