lensapp/lens

HPA external metrics values show 0 incorrectly

Open

#6068 opened on Aug 20, 2022

View on GitHub
 (2 comments) (3 reactions) (0 assignees)TypeScript (22,003 stars) (1,433 forks)batch import
area/uibuggood first issue

Description

Describe the bug HPA external metric values are displayed with the value 0 when these are actually different

To Reproduce Steps to reproduce the behavior:

  1. Connect to a cluster with HPA using External metrics, e.g. KEDA
  2. See 0 / X in Metrics column and details view (X is target value)

Expected behavior Actual metric values are displayed

Screenshots

Environment (please complete the following information):

  • Lens Version: 6.0.1-latest.20220810.2
  • OS: macOS Ventura 13.0 Beta (22A5321d)
  • Installation method (e.g. snap or AppImage in Linux): Intel dmg from k8slens.dev

Logs: Nothing relevant except:

info:    ▪ Creating a new port-forward system/service/keda-operator-metrics-apiserver:9022 +3s

The port forward seems intact:

Contributor guide

Tech stack
typescriptreactelectron
Domain
frontenddesktop
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic understanding of Kubernetes HPAFamiliarity with React componentsTypeScript basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
The bug is in the HPA details view where external metric values display as 0. Look at the component that renders HPA metrics, likely in the 'pods' or 'hpa' directory. Check how the current value is retrieved from the Kubernetes API; external metrics might be stored differently. Investigate if the metric value is being parsed correctly from the response. The issue mentions KEDA, so ensure the code handles custom metrics providers. No linked PRs or assignees suggest it's available for contribution.