Kibana pod will fail with error "KIBANA_MEMORY_LIMIT: unbound variable"

Solution In Progress - Updated -

Environment

OpenShift Container Platform 3.5

Issue

When running the Kibana pod, the logs shows error KIBANA_MEMORY_LIMIT: unbound variable.

Resolution

Edit the Deployment Config of the Kibana and add the KIBANA_MEMORY_LIMIT variable, as shown below.

spec:
      containers:
      - env:
        - name: ES_HOST
          value: logging-es
        - name: ES_PORT
          value: "9200"
        - name: KIBANA_MEMORY_LIMIT
          value: 736Mi

Root Cause

The Kibana variable is required to be configured. If upgrade of the image was done and the Deployment Config does not have the env, it will fail.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments