Join fellow LogicMonitor users at the Elevate Community Conference and get hands-on with our latest product innovations.

Register Now

Resources

Explore our blogs, guides, case studies, eBooks, and more actionable insights to enhance your IT monitoring and observability.

View Resources

About us

Get to know LogicMonitor and our team.

About us

Documentation

Read through our documentation, check out our latest release notes, or submit a ticket to our world-class customer service team.

View Resources

Troubleshooting Kubernetes Upgrade Issues

Last updated on 29 April, 2024

kube-state-metrics (KSM) is not Discoverable

Cause

When you use the command-line interface (CLI) to upgrade the Kubernetes cluster from 4.0.0 to 5.0.0 or later, kube-state-metrics (KSM) is not discoverable because the KSM image URL has an extra registry name appended.

Resolution

You need to add the following parameters to the lmc-configuration.yaml file:

kube-state-metrics:
  enabled: true
  image:
    registry: registry.k8s.io
    repository: kube-state-metrics/kube-state-metrics
    tag: v2.10.0

Helm Upgrade is Failing

Cause

When you use the command-line interface (CLI) to upgrade the Kubernetes cluster from 4.3.0 or lower to 4.4.0 or later, the helm upgrade fails due to missing subcharts data for LM OTEL(OpenTelemetry) and LM-Logs in LM Container helm charts. 

Resolution

You need to add the following parameters to the lmc-configuration file:

lmotel:
  enabled: false
lm-logs:
  enabled: false
In This Article

Start Your Trial

Full access to the LogicMonitor platform.
Comprehensive monitoring and alerting for unlimited devices.